batch-sync-changes-through-a-queue

Use it when

• A sync sees more than a few hundred changed records per hour, or bursts of 1,000 or more.
• The next step can take records as a list: a bulk API call, a file, one database statement.
• A wait of up to 60 seconds (the default maximum age) between the change and the action is fine.

Why this design

Advantages:

• One run per batch instead of one per record: 5,000 changes at the default batch size of 1,000 start 5 runs, not 5,000.
• Runs stay under the limit of 20 concurrent runs per workflow, so nothing waits for a slot.
• Flush rules set the pace: batch size (default 1,000, up to 10,000), maximum age (default 60 seconds, up to 86,400) and flushes per time window.
• Records wait in the queue while the consumer workflow is paused, so a fix does not lose them.