:zap: Workflow Automation Platform. Orchestrate & Schedule code in any language, run anywhere, 500+ plugins. Alternative to Zapier, Rundeck, Camunda, Airflow...
We have encountered a rather interesting scheduler behavior during regular operation.
TL;DR
The scheduler does not trigger an execution when the scheduler flow definition gets upgraded via the flow namespace update CLI command issued at the time of the execution.
Description
It seems the trigger scheduler gets interrupted by a deployment of new flows. In our environment there are multiple flow definition deployments happening daily via CI/CI using the flow namespace update CLI command.
It is rather unacceptable to miss triggers scheduled to run daily or even weekly in production.
Example
Output of import CLI command issued at 09:53:59,111:
Describe the issue
We have encountered a rather interesting scheduler behavior during regular operation.
TL;DR
The scheduler does not trigger an execution when the scheduler flow definition gets upgraded via the
flow namespace update
CLI command issued at the time of the execution.Description
It seems the trigger scheduler gets interrupted by a deployment of new flows. In our environment there are multiple flow definition deployments happening daily via CI/CI using the
flow namespace update
CLI command.It is rather unacceptable to miss triggers scheduled to run daily or even weekly in production.
Example
Output of import CLI command issued at 09:53:59,111:
Execution history of one of the imported flows is missing the execution which would be triggered at 09:54:
Reproduction steps
First of all, the reproduction rate not 100% since it relies on timing.
flow_imports
flow_imports/myflow.yaml
flow_imports/myflow.yaml
file:./kestra server local
./kestra flow namespace update 'company.team' '<path_to>/flow_imports'
CLI commandEnvironment