My Flow stopped working after I moved it to another project

Last updated: October 21, 2026

Symptoms

After moving a Flow from one project to another - commonly from your personal sandbox to a shared project you may notice that the triggers stop firing. No error appears anywhere; the Flow just goes quiet. For example, Slack messages may still post, but clicking a button does nothing.

Why this happens

App installations belong to the project, not to the Flow. Moving a Flow does not move its app installations, and it does not re-link the blocks. Your blocks are still pointing at installations that live in the project you moved away from.

For Slack this is especially visible, because the Interactivity and Events request URLs in your Slack app config point at the app installation's endpoint subdomain. After a move, Slack is still delivering to the old installation, so interactions are accepted and then dropped. A Flow's own subdomain will return 404 on /interactivity — those routes only exist at installation level.

Fix

  1. In the destination project, install every app the Flow needs. Go to Installations in the project's left panel.

  2. Open the original Flow, select the blocks, and copy them (Cmd/Ctrl+C). They copy as YAML.

  3. Create a new Flow in the destination project and paste (Cmd/Ctrl+V).

  4. Check each block is pointing at the destination project's installation. You can reassign a block to a different installation from the block's config.

  5. If you use Slack interactivity, update your Slack app's Interactivity & Shortcuts and Event Subscriptions request URLs to the destination installation's endpoint. Take the URL from the installation itself rather than typing it - a mismatch here fails silently.

  6. Give anyone who needs to see the Flow access to the project. Organization membership on its own is not enough. See Flow Navigation & Organization.

Checking it worked

Open the app installation and go to Debug → HTTP. Incoming requests appear here, and a 403 usually means a signing key mismatch. If the Flow is triggered by Slack interactions, click a button and confirm the request lands.

Avoiding it

Build the Flow in the project where it's going to live. If you're prototyping in a sandbox and expect to promote it later, install the apps in the destination project up front. Treat a move as a rebuild rather than a drag-and-drop.