Activepieces Runs Stuck in Queued

How to fix it

Try these in order — the most common fix is first.

1. 1. Check and cancel runs

   Copy steps
   1. Open the project run history
   2. Count running flows against the limit
   3. Select unneeded queued runs and click Cancel
   Did this fix it? Yes No

2. 2. Spread out the load

   Copy steps
   1. Move heavy schedules off the top of the hour, for example cron 5 * * * *
   2. Send more rows per run in batch flows
   3. Add filters so flows stop early
   Did this fix it? Yes No

3. 3. Self-hosted capacity

   Copy steps
   1. Check Platform Admin, Operations, Health, Queue Health
   2. Add workers or raise AP_DEFAULT_CONCURRENT_JOBS_LIMIT
   3. Use persistent storage for Redis
   Did this fix it? Yes No

4. 4. Contact support if it persists

   Copy steps
   1. Email support with the run link
   2. A run queued for a week is treated as a bug by staff
   Did this fix it? Yes No

Symptoms

Runs show Queued and do not start, or a batch stops after a few runs.

Why it happens

• Project concurrency limit reached
• Burst of triggers or Call Flow loops
• All workers busy on self-hosted
• Worker group with no online workers (Enterprise)
• Redis lost its data

This guide also covers

• activepieces stuck in queued
• activepieces queued runs not executing
• activepieces flow stuck running

Other Activepieces errors

• Activepieces Webhook Not Triggering
• Activepieces EXECUTION_TIMEOUT Error
• Activepieces Code Step Out of Memory
• Activepieces Flow Shows Success but Step Failed
• Activepieces Self-Hosted Docker Not Working
• Activepieces Upgrade Broke Flows
• Activepieces Connection Expired or Authorization Failed
• Activepieces Flow Won't Turn On or Stops Running