Open
Description
Is your feature request related to a problem? Please describe.
Outbound connectors are affected by Zeebe's job timeout mechanism:
- by default it's 5 minutes
- if connector takes too long to execute, the job will be considered failed by the engine and reassigned
- on the other hand, if the pod restarts mid-execution, we have to wait the default 5 minutes before it gets retried
Describe the solution you'd like
We'd like to expose the job timeout as a property in element templates.
- It can be a job header
- When the connector job handler starts, we check if this job header is present, and if it is, we run an
UpdateJobTimeoutCommand
via the Zeebe client.
Describe alternatives you've considered
none so far
Additional context