---
title: Task Manager settings in Kibana
description: 
url: https://www.elastic.co/elastic/docs-builder/docs/3174/reference/kibana/configuration-reference/task-manager-settings
products:
  - Kibana
applies_to:
  - Self-managed Elastic deployments: Generally available
---

# Task Manager settings in Kibana
Task Manager runs background tasks by polling for work on an interval. You can configure its behavior to tune for performance and throughput.

## Task Manager settings
<definitions>
  <definition term="xpack.task_manager.max_attempts">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

The maximum number of times a task will be attempted before being abandoned as failed.
Datatype: `int`
Default: `3`
  </definition>
  <definition term="xpack.task_manager.poll_interval">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

How often, in milliseconds, the task manager will look for more work. Cannot be lower than 100.
Datatype: `int`
Default: `500`
  </definition>
  <definition term="xpack.task_manager.request_capacity">
    <supported-on>Self-managed Elastic deployments: Generally available</supported-on>

How many requests can Task Manager buffer before it rejects new requests.
Datatype: `int`
Default: `1000`
  </definition>
  <definition term="xpack.task_manager.max_workers">
    <stack-availability>Elastic Stack: Deprecated since 8.16</stack-availability>
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

The maximum number of tasks that this Kibana instance will run simultaneously. Starting in 8.0, it will not be possible to set the value greater than 100.
Datatype: `int`
Default: `10`

<admonition title="Deprecation details">
  This setting was deprecated in 8.16.0.
</admonition>

  </definition>
  <definition term="xpack.task_manager.monitored_stats_health_verbose_log.enabled">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

This flag will enable automatic warn and error logging if task manager self detects a performance issue, such as the time between when a task is scheduled to execute and when it actually executes.
Datatype: `bool`
Default: `false`
  </definition>
  <definition term="xpack.task_manager.monitored_stats_health_verbose_log.warn_delayed_task_start_in_seconds">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

The amount of seconds we allow a task to delay before printing a warning server log.
Datatype: `int`
Default: `60`
  </definition>
  <definition term="xpack.task_manager.event_loop_delay.monitor">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Enables event loop delay monitoring, which will log a warning when a task causes an event loop delay which exceeds the `warn_threshold` setting.
Datatype: `bool`
Default: `true`
  </definition>
  <definition term="xpack.task_manager.event_loop_delay.warn_threshold">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Sets the amount of event loop delay during a task execution which will cause a warning to be logged.
Datatype: `int`
Default: `5000`
  </definition>
  <definition term="xpack.task_manager.capacity">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Controls the number of tasks that can be run at one time. The minimum value is 5 and the maximum is 50.
Datatype: `int`
Default: `10`
  </definition>
</definitions>

## Task Manager health settings

Settings that configure the [Health monitoring](https://www.elastic.co/docs/deploy-manage/monitor/kibana-task-manager-health-monitoring) endpoint.
<definitions>
  <definition term="xpack.task_manager.monitored_task_execution_thresholds">
    <supported-on>Elastic Cloud Hosted: Generally available, Self-managed Elastic deployments: Generally available</supported-on>

Configures the threshold of failed task executions at which point the `warn` or `error` health status is set under each task type execution status (under `stats.runtime.value.execution.result_frequency_percent_as_number[${task type}].status`).
This setting allows configuration of both the default level and a custom task type specific level. By default, this setting is configured to mark the health of every task type as `warning` when it exceeds 80% failed executions, and as `error` at 90%.
Custom configurations allow you to reduce this threshold to catch failures sooner for task types that you might consider critical, such as alerting tasks.
This value can be set to any number between 0 to 100, and a threshold is hit when the value **exceeds** this number. This means that you can avoid setting the status to `error` by setting the threshold at 100, or hit `error` the moment any task fails by setting the threshold to 0 (as it will exceed 0 once a single failure occurs).
Datatype: `int`
  </definition>
</definitions>