Activepieces Upgrade Broke Flows

How to fix it

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

1. 1. Check the breaking changes

   Copy steps
   1. Read the breaking-changes page for every version you skipped
   2. Compare your compose file with the official one
   Did this fix it? Yes No

2. 2. Roll back

   Copy steps
   1. Restore the pre-upgrade dump with pg_restore into a fresh database
   2. Switch docker-compose.yml back to the previous image
   3. Start Activepieces
   Did this fix it? Yes No

3. 3. Upgrade safely next time

   Copy steps
   1. Dump the database
   2. Run docker compose pull and up -d
   3. Open a few existing flows to verify
   Did this fix it? Yes No

Symptoms

Flows list empty after upgrade, flows fail, or templates break.

Why it happens

• Skipped release notes
• Changed Postgres image
• Breaking changes in a version

This guide also covers

• activepieces upgrade broke flows
• activepieces flows missing after upgrade

Other Activepieces errors

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