v6.5.0
New features:
- You can now specify a retry policy for process chains. This policy defines how often a process chain should be retried after it has failed and how long Steep should wait between attempts. It can be specified on a workflow-level and applies to all process chains generated from the workflow.
- A new process chain status
PAUSED
has been added. Process chains with this status are subject to being retried eventually according to their retry policy. - The
/processchains
endpoint has been extended so you can fetch information about a specific run (i.e. attempt) of a process chain (/processchains/:id/runs/:runNumber
) - The
/logs/processchains
endpoint has been extended so you can fetch the logs of a specific process chain run - The process chain data model has been extended to include the run number, the total number of runs, and an optional
autoResumeAfter
timestamp, which denotes when the next attempt will happen - It is now possible to specify a whitelist for HTTP routes. This allows you to enable the HTTP server with subset of endpoints (e.g. if you only want to enable the
/metrics
endpoint but nothing else on agents)
Bug fixes:
- Improved legibility in web UI: Text inside labels does not wrap anymore but a long list of labels still does
- Prevent two schedulers from looking for orphans at the same time. This avoids race conditions that could, in rare cases, lead to a process chain being scheduled twice on different agents.
- Increase timeout for sending process chain results to scheduler
Maintenance:
- The workflow API version is now 4.6.0
- Replace Vert.x Lock with ClusterSemaphore to avoid unnecessary Hazelcast CP group commits
- Disable unnecessary Hazelcast log message
- Update to Kotlin 1.8
- Update to Next.js 13
- Update other dependencies
- A few internal refactorings