Blocked Deployments after Shopify Flow Extension Migration

We migrated our Shopify Flow extensions to the new uid setup.

However, on our next deployment we were shown the following error

The action:

[[extensions]]

uid = “4863b37f-24d4-d943-0177-dc665d25b99b49e02e62”

type = “flow_action”

name = “Add Store Credit for a Custom Action”

handle = “action-add-store-credit-for-a-custom-action”

The issue here is that the handle must match the Shopify Flow Action name we are mapping to. So there is no way for me to shorten this and not delete the existing flow action.

Has anyone experienced this so far or is this a known bug?

Hey Stuart, that error is coming from the Flow action handle length. Handles are kebab-case identifiers with a max of 40 characters, while the merchant-facing “name” can be longer. Your handle is 43 chars, so the deploy fails even though the name is fine (Create a Flow action)

You can keep the full display name, but you’ll need to shorten the handle, e.g. add-store-credit-custom-action, to publish a new version.

Also, the handle doesn’t have to match the action name; it’s just the unique ID Flow tracks for the action definition. Changing it effectively creates a new action definition, so existing Flows wired to the old handle won’t auto-migrate. In practice I ship the new action with a shortened handle, leave the old one in place, and communicate a quick re-save/migrate step to merchants before removing the legacy action (Flow action reference).

If you absolutely must preserve the old Flows without any touch, keep the legacy handle published and add the new, shorter handle in parallel until you can coordinate the switch.

Thanks for the reply @Ruben_Stacksync

communicate a quick re-save/migrate step to merchants

this seems kind of crazy - especially across hundreds/thousands of brands no? :melting_face: