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
The AWS SQS Trigger in Kestra is exhibiting unexpected behavior where it executes previous revisions of a flow randomly instead of the latest version. The trigger configuration is as follows:
While the trigger works as expected in terms of functionality, it inconsistently executes older revisions of the script rather than the latest one. This issue seems to occur particularly when there are multiple revisions of the flow.
Steps to Reproduce:
Set up a Kestra flow with the provided SQS trigger configuration.
Create multiple revisions of a flow.
trigger SQS event
Observe the trigger executing previous revisions randomly instead of the latest one.
Additional Context:
The issue persists even when reducing the deployment to a single scheduler pod.
Manually executing the flow using the execute button correctly utilizes the latest revision.
Using a lambda function to process the event in SQS and trigger the Kestra job via webhook works as expected, indicating a potential issue with the SQS trigger.
Upon inspecting the scheduler with curl http://localhost:8081/scheduler, an empty dictionary is returned, suggesting another underlying issue.
Environment
Kestra Version: 0.15.5
Operating System (OS/Docker/Kubernetes): Kubernetes multi node
The text was updated successfully, but these errors were encountered:
The AWS SQS Trigger in Kestra is exhibiting unexpected behavior where it executes previous revisions of a flow randomly instead of the latest version. The trigger configuration is as follows:
While the trigger works as expected in terms of functionality, it inconsistently executes older revisions of the script rather than the latest one. This issue seems to occur particularly when there are multiple revisions of the flow.
Steps to Reproduce:
Additional Context:
curl http://localhost:8081/scheduler
, an empty dictionary is returned, suggesting another underlying issue.Environment
The text was updated successfully, but these errors were encountered: