You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer, I know that my worker needs time to process
In Zeebe, you can tell the engine that you need time to do it: this is the timeout. After this timeout, Zeebe considers the worker/connector is dead, and unlocks it; then a new worker can take it
As a developer, I want to give two information then:
This timeout (for example, 30 seconds)
if this timeout depends on the number of threads
It will be possible for the administrator to change the number of threads. By default, this is one. But if the admin setup this parameter to 32, we can assume the needed time is then *32... or not.
The text was updated successfully, but these errors were encountered:
As a developer, I know that my worker needs time to process
In Zeebe, you can tell the engine that you need time to do it: this is the timeout. After this timeout, Zeebe considers the worker/connector is dead, and unlocks it; then a new worker can take it
As a developer, I want to give two information then:
It will be possible for the administrator to change the number of threads. By default, this is one. But if the admin setup this parameter to 32, we can assume the needed time is then *32... or not.
The text was updated successfully, but these errors were encountered: