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
After version 0.23.0, I've consistently run into the following issue when a cron task gets triggered, which then causes a reboot loop on the engine container:
Hey @trisongz, thanks for the report - I'll be taking a look at this today. This looks like an issue with the workflow run not being created properly from cron workflows if you have a concurrency limit setting on the workflow run. This isn't an issue with RabbitMQ, so no need to restart things on that side (the methods are just being triggered by a RabbitMQ message).
abelanger5
changed the title
bug: rabbitmq subscribe issue with hatchet-engine > 0.23.0
bug: crons with concurrency limits set cause the engine to crash
May 11, 2024
I have hatchet self-hosted in a K8s cluster.
Container Images:
ghcr.io/hatchet-dev/hatchet/hatchet-engine:v0.26.1
ghcr.io/hatchet-dev/hatchet/hatchet-api:v0.26.1
docker.io/bitnami/rabbitmq:3.13.2-debian-12-r0
SDK: Python -
hatchet-sdk-0.23.0
(0.22.5
prior)After version
0.23.0
, I've consistently run into the following issue when a cron task gets triggered, which then causes a reboot loop on theengine
container:I've attempted the following to debug:
engine
container to get back up.rabbitmq
, including the persistent data, which doesn't do anything.I am able to trigger the workflow manually, but whenever the cron schedule triggers the workflow, that issue occurs.
The text was updated successfully, but these errors were encountered: