Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trigger is not cleaned when the concurrency limit is reached #6889

Open
tchiotludo opened this issue Jan 22, 2025 · 0 comments
Open

Trigger is not cleaned when the concurrency limit is reached #6889

tchiotludo opened this issue Jan 22, 2025 · 0 comments
Assignees
Labels
area/backend Needs backend code changes bug Something isn't working

Comments

@tchiotludo
Copy link
Member

You have a trigger every hour, with concurrency set with cancelled

concurrency:
  behavior: CANCEL
  limit: 1

If a flow is manually triggered and end after the schedule, the triggered execution will be CANCELLED, fine.
But the trigger will not cleaned the execution id, leading to locking the schedule, with this logs:

Execution '6hjH3zCN4e6yDczobgnSgh' is not found, schedule is blocked since '2025-01-22T14:00:02.350299Z'

A user on the EE kafka version:
Image

It's theory here, that need to be validated

@tchiotludo tchiotludo added area/backend Needs backend code changes bug Something isn't working labels Jan 22, 2025
@github-project-automation github-project-automation bot moved this to Backlog in Issues Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/backend Needs backend code changes bug Something isn't working
Projects
Status: Backlog
Development

No branches or pull requests

2 participants