We are facing an issue with the SQL Server 5-minute interval polling trigger recipe.
The trigger recipe is already in Started state.
When we update a record in SQL Server, the job is picked up after some time and starts processing, which is expected.
However, during this processing time, if we update another record (without refreshing the recipe and without clicking Check for jobs), that second update is getting skipped.
After waiting for the next 5-minute polling interval, we observed the following message:
"Last checked at Jan 13, 2026, 4:21:59 AM PST Found 1 job, queued it for processing. Skipped 1. Current queue size: Approx. 1 job Estimated time to clear queue: less than a minute"
Only one record/job gets processed, while the record updated during the ongoing processing is skipped.
Expected Behavior:
All records updated in SQL Server should be captured and queued for processing by the polling trigger, even if they are updated while another job is already being processed.
No record should be skipped as long as it meets the trigger conditions.
Actual Behavior:
When multiple records are updated within the same polling window and one is already under processing, the subsequent update is skipped.
