Hi team,
I’m using a Cursor Automation with the trigger set to “Push to main” on my repository.
My use case is that every push to the main branch should trigger a code scan, and I expect all runs to execute independently. Running multiple scans concurrently is completely acceptable and actually required for my workflow.
Previously, this worked as expected. If multiple pushes happened around the same time, Cursor would start multiple automation runs and all of them would complete successfully.
However, since around June 18, 2026 (Indonesia time / UTC+7), the behavior seems to have changed.
What happened before
- Push #1 → Automation starts
- Push #2 → Automation starts
- Push #3 → Automation starts
- All runs execute and complete successfully, even if they overlap in time
Current behavior
When multiple pushes happen close together:
- The newest run starts normally
- Previous runs are automatically cancelled
- The cancelled run shows:
Cancelled by newer run
And the details say:
This run was cancelled because a newer event arrived for the same target (push, PR update, or CI completion). The newer run is handling the latest state.
What I need
I do not want newer pushes to cancel older runs.
My goal is:
- Every push event should create its own automation run
- All runs should be allowed to execute concurrently
- No automatic cancellation when a newer push arrives
- Each push should perform its own code scan, regardless of whether another run is already in progress
Question
Has there been a recent change to automation concurrency or cancellation behavior?
Is there any setting, configuration, or recommended approach that allows all push-triggered automation runs to execute independently without being cancelled by newer runs?
I would like the behavior to be the same as before, where concurrent push-triggered runs were all allowed to complete successfully.
Thanks!
