From 0d9bebc4603a82e1d2b5e8c6902ab05062f5d938 Mon Sep 17 00:00:00 2001 From: RizaFarheen Date: Wed, 13 Nov 2024 11:45:03 +0400 Subject: [PATCH] Update creating-task-definitions.md --- docs/reference-docs/api/metadata/creating-task-definitions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference-docs/api/metadata/creating-task-definitions.md b/docs/reference-docs/api/metadata/creating-task-definitions.md index c5047603..0a5a629e 100644 --- a/docs/reference-docs/api/metadata/creating-task-definitions.md +++ b/docs/reference-docs/api/metadata/creating-task-definitions.md @@ -27,7 +27,7 @@ Task definitions register tasks in Conductor. This API is used to create task de | concurrentExecLimit | The number of tasks that can be executed at any given time.

For example, if you have 1000 task executions waiting in the queue and 1000 workers polling this queue for tasks, but if you have set _concurrentExecLimit_ to 10, only 10 tasks would be given to workers (which would lead to starvation). If any of the workers finish execution, a new task(s) will be removed from the queue while still keeping the current execution count to 10. | | backOffScaleFactor | The value to be multiplied with retryDelaySeconds in order to determine the interval for retry. | | rateLimitFrequencyInSeconds, rateLimitPerFrequency | Rate limiting is only supported for the Redis persistence module and is unavailable with other persistence layers.

For example, let’s set **rateLimitFrequencyInSeconds=5**, and **rateLimitPerFrequency=12**. This means our frequency window is 5 seconds in duration, and for each frequency window, the Conductor would only give 12 tasks to workers. So, in a given minute, the Conductor would only give 12*(60/5) = 144 tasks to workers, irrespective of the number of workers polling for the task.
Unlike **concurrentExecLimit**, rate limiting doesn't consider the tasks already in progress or a terminal state. Even if all the previous tasks are executed within 1 sec or would take a few days, the new tasks are still given to workers at configured frequency, 144 tasks per minute in the above example. | -| enforceSchema | Set to `true` to enforce task inputs/outputs for all instances of the task. By default, the value is set to ‘false’. | +| enforceSchema | Set to `true` to enforce task inputs/outputs for all instances of the task. By default, the value is set to `false`. | | inputSchema | If _enforceSchema_ is set to `true`, select a schema (and version) to be used as input schema for the task definition. Learn more about [creating and using schema](https://orkes.io/content/developer-guides/schema-validation). | | outputSchema | If _enforceSchema_ is set to `true`, select a schema (and version) to be used as output schema for the task definition. Learn more about [creating and using schema](https://orkes.io/content/developer-guides/schema-validation). | | ownerEmail | This field will be auto-populated with the user's email address. |