Einführung
A device can only have one active run per trigger at a time. If a device is already in the pipeline for a given automation (running, waiting for approval, or queued as "when next online"), a subsequent firing of the same trigger won't add it again. The duplicate is silently dropped.
How Duplicate Prevention Works
When a trigger fires, Level checks whether each matching device already has an active run in that automation's pipeline. If a device is already there in any state, the trigger skips it.
The practical effect: if a device goes offline during a scheduled automation run and stays offline for an extended period, it stays queued in the pipeline as "when next online." Subsequent scheduled firings of that same trigger won't re-add it. The device has one slot in the pipeline, and it's occupied until the current run completes or is manually removed.
This applies per trigger, not per automation. If an automation has two different triggers (for example, a Scheduled trigger and a Tag Applied trigger), a device could theoretically be in the pipeline twice — once per trigger. But the same trigger won't create a second run for a device that's already active.
ℹ️ NOTE: Once the current run finishes (succeeds, fails, or is manually cancelled), the device can be added again by the next trigger firing.
Checking Active Runs
To see which devices are currently in an automation's pipeline:
Open the automation.
Look at the Active devices count in the bottom left of the left sidebar.
Click View all to see the current state of each device (Running, Waiting on approval, When next online).
From this view, you can remove a device from the pipeline manually if you need to clear its slot before the next trigger fires.
Häufig gestellte Fragen
A device has been offline for days. Will it still run when it comes back online? Yes. It stays queued in the pipeline. When the device checks in, the run resumes. It won't have been re-added by subsequent trigger firings — it has one queued run that was waiting.
What if I want to force a fresh run even though the device already has an active one? Remove the device from the current pipeline manually (via the Active devices panel), then either wait for the next trigger firing or add it manually using + Add a device in the automation's pipeline view.
Does this apply to manual runs as well? Yes. If you manually add a device to an automation that it's already active in, the manual addition is also blocked. The device can only occupy one active run per trigger at a time.