Flow does not exist but still running it

[Daniele Vieira Campbell]

A flow was created a long time ago, and we would like to disable it. However, when we click on the 'Automation' link, it states that the flow does not exist. We have tried searching under 'Scope: All flows', but the flow still cannot be found. How can I locate this flow to disable it?

[Mikael Sandberg]

Hi @Daniele Vieira Campbell,

Welcome to Atlassian Community!

Have you checked Settings > Systems > Global automations? From here you can also go into the Audit log tab and search for a work item that you suspect the flow is running on to see which flows triggered on that specific work item. 

[Marc -Devoteam-]

Hi @Daniele Vieira Campbell 

@Mikael Sandberg is completely right here.

The flow is probably a multi-space or global flow and than can only be disabled from global automation by a JIra admin.

[Daniele Vieira Campbell]

Thank you! I will check with Jira Admin

[James Gamble]

Hi Daniele,

@Mikael Sandberg and @Marc -Devoteam- are probably right that this is a multi-space or global flow that only a Jira admin can manage. Your screenshots show that you’re searching from the OTS Supervisor Tasks space settings, and even with Scope set to All flows, that view may not expose flows you don’t have permission to edit.

The Recent rule runs panel is a useful clue here. It shows that “Internal handover” ran recently, but clicking Configure leads to “This flow doesn’t exist.” That message can also mean the flow exists, but your account can’t view it, rather than that it was actually deleted.

Ask a Jira admin to open Settings > System > Global automation, then check the Audit log and search for “Internal handover” or one of the affected work item keys. The global audit log covers flows across Jira and should reveal the flow name, Scope, and recent executions.

If the flow still appears in the global audit log but the admin also receives “This flow doesn’t exist,” that suggests a stale or orphaned flow record rather than a normal permissions issue. At that point, I’d open an Atlassian Support case and include the screenshots, the flow name, the affected work item key, the execution time, and the audit log ID.

Thanks,

James