Flow Trigger ExtensionsFlow Trigger Extensions

Report a bug

Report a bug

Something in Workflow Trigger Extensions is broken or behaving unexpectedly. The more precisely you can point at it, the faster we can fix it.

Drop a file here, or click to choose

Before you send: Event history and troubleshooting resolves most reports in a couple of minutes. The usual causes are a permission that was never granted, a baseline sync that has not finished yet, or an exhausted monthly quota.

If it is still wrong after that, the form above is the fastest route.

What makes a report easy to fix

The four things that let us trace an event end to end:

  1. Your store domain - so we can find the event.
  2. The trigger name, exactly as it appears in Shopify Flow, for example Product Variant Price Changed.
  3. An approximate timestamp of the change you expected to fire.
  4. What Event History showed for that moment, if anything.

With those we can follow the event from Shopify's webhook all the way through to the Flow trigger delivery.

Useful things to attach

  • A screenshot of Event History, or of the event detail page.
  • A screenshot of your Shopify Flow workflow, showing the trigger step.
  • A screenshot of the Permissions page if you suspect a data-access problem.
  • An export of the workflow (.flow) if the problem is in how it is wired up.

Prefer another channel?

  • In-app chat - open any page of the app in your Shopify admin and use the chat bubble. This is the fastest route and keeps the report tied to your store.
  • Email - support@codecreationlabs.com. Include your store URL so we can follow up.
  • Slack - join our apps workspace, linked from Support.

Missing something rather than broken?

If the app is working as designed but does not do what you need, Request a feature instead. Bugs jump the queue; feature requests are grouped so repeated asks carry weight.