Configure concurrent execution

Coordinate repeated triggers and shared outputs.

Before you start

Use a test project connected to Core. Review Apply and Save before testing a changed definition.

Steps

1. Identify which events share an output, such as one OBS overlay or speech channel.
2. Choose the automation's concurrency mode: queue required reactions, run independent work in parallel, or deliberately replace/suppress repeated work.
3. Set queue or parallel limits and review overflow behavior.
4. If several automations share the same output, place them behind the appropriate folder concurrency boundary.
5. Save the automation, trigger a controlled burst and inspect execution order in Runs.

Verify

Accepted work follows the selected coordination policy. Inspect the corresponding run, then Save the applied project when the result is correct.

If it does not work

A dropped event does not refund a donation or reward. Cooldown timing and keys are separate decisions; see Concurrency.