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
UPD: I've went back to 17.8 and the problem has disappeared.
I guess it would be nice to introduce some sort of compatibility checks between Kestra and plugins versions.
Also, the system should report some compatibility issues during startup when upgrading/downgrading
UPD: the same problem happens after I went back to 17.5 version. this time it is a cron-based trigger
I have a couple of flows with kafka triggers and clickhouse triggers
Flows were running smoothly with kestra 17.4 and 17.5
Once I've updated to 17.8 following problem has happened:
A flow creates a new execution that stucks in "CREATED" state.
If I click on the execution id in a global Executions tab or from the flow's Execution tab a message with "execution not found" pops up. However I can delete it by checking a box near to the execution id and clicking on DELETE button.
Also, I've checked that execution's data is available in S3 storage.
I had to downgrade back to 17.5 to make the flows running again. In 17.8 triggered executions stuck in CREATED state
Environment
Kestra Version: 0.17.8
Operating System (OS/Docker/Kubernetes): standalone binarie
Java Version (if you don't run kestra in Docker):
The text was updated successfully, but these errors were encountered:
aku
changed the title
Upgrading kestra from 17.5 to 17.8 breaks flows with triggers
Upgrading kestra from 17.5 to 17.8 breaks triggered flows executions
Jul 1, 2024
I've went back to 17.8 and the problem has disappeared.
I guess it would be nice to introduce some sort of compatibility checks between Kestra and plugins versions.
Also, the system should report some compatibility issues during startup when upgrading/downgrading
Describe the issue
UPD: I've went back to 17.8 and the problem has disappeared.
I guess it would be nice to introduce some sort of compatibility checks between Kestra and plugins versions.
Also, the system should report some compatibility issues during startup when upgrading/downgrading
UPD: the same problem happens after I went back to 17.5 version. this time it is a cron-based trigger
I have a couple of flows with kafka triggers and clickhouse triggers
e.g.:
Flows were running smoothly with kestra 17.4 and 17.5
Once I've updated to 17.8 following problem has happened:
A flow creates a new execution that stucks in "CREATED" state.
If I click on the execution id in a global Executions tab or from the flow's Execution tab a message with "execution not found" pops up. However I can delete it by checking a box near to the execution id and clicking on DELETE button.
Also, I've checked that execution's data is available in S3 storage.
I had to downgrade back to 17.5 to make the flows running again. In 17.8 triggered executions stuck in CREATED state
Environment
The text was updated successfully, but these errors were encountered: