react-to-each-record-change

Use it when

• Each changed record needs its own action: a message, an API call, a record in another app.
• Changes stay under about 20 at the same moment and a few hundred per hour. The engine runs at most 20 runs of one workflow at a time; more changes wait for a free slot.
• The action can run within seconds of the change.

Above that volume, or when the receiving app limits calls, use batch-sync-changes-through-a-queue.

Why this design

Advantages:

• One run per record: each run is short, its input is one record, and a failed run names the record that failed.
• No batching code: steps read the record directly.