How-to
Short answer: Both statuses mean the run is waiting its turn. Kissflow holds extra runs when many are requested at once, then starts them automatically. You don't need to do anything.
Why it happens
Kissflow limits how many integration runs execute at the same time. When a burst of runs arrives, the extra ones wait instead of failing on rate limits.
- Queued: the run is waiting, and starts when one of the running integrations finishes.
- Not Started: several integrations tried to run at once under heavy load. The run starts once the load drops.
How to fix it
- Wait a few minutes. Both statuses clear on their own, though the run may finish later than usual.
- Open Explore > Managed by me > Integrations > Run history to follow the run. See Run history.
- If a run stays in either status for a long time, or ends as failed, note the run ID and contact Kissflow support.
Important
Queue and throttling details aren't visible in your account. Expect some runs to wait when many items are submitted at the same moment.