Jira Cloud automation still running but rule no longer exists

Question

Hi,

We're experiencing a strange issue with a Jira Cloud automation rule.

We had an automation configured with a monthly scheduled trigger, based on a specific day and time.

The problem is that the automation is still running, but the rule is no longer visible in the automation list.

Here's what we've observed:

* The automation continues to execute every month.
* Its executions are visible in the automation audit log.
* The rule doesn't appear in the automation list, even when accessing it with full Jira administrator permissions.
* Clicking the automation link from the audit log returns an error stating that "Automation doesn't exist."

We've checked the automation list with administrator permissions but haven't been able to locate the rule.

It seems that the scheduled trigger is still active, even though the rule itself is no longer accessible.

Is there a way to locate and disable an automation that continues running but is no longer visible in Jira Cloud?

Any suggestions would be greatly appreciated.

Thanks in advance!

Alessandro Casciaro · Answer

Mystery solved! For some inexplicable reason, the automation was in a different space (Space A), but it was still creating tickets in Space B.

Thanks for your help!

Tomislav Tobijas · Answer

@Alessandro Casciaro never seen this but I won't say I'm surprised 😅

You could try to force a UI and cache refresh (e.g., try incognito mode and/or search by name). It might also be that there's a bug between the automation engine and the front-end, but that might need Atlassian Support assistance if it doesn't resolve itself 👀

🤔 Could it be a legacy automation? You could check this by navigating to Space settings > Automation > Legacy automation

Anyway, support should be able to check it out (that's if you're on a paid plan).

Cheers,

Tobi

Daniel Brooks · Answer

One extra angle that helped us separate a real ghost rule from a look-alike: check what the monthly run actually does in the issue history. If the changes show the actor as Automation for Jira, it is a rule on this site. If the actor is a different app user, look for a scheduled job in that app instead, because those keep running even when the original rule is gone.

While you wait on Support, you can also contain it in the projects it touches. Rules act through the Automation for Jira actor, so temporarily removing that actor from the relevant permission (for example Edit issues or Create issues) in those projects' permission schemes will stop the actions landing. It will pause your other rules in those projects too, so note which ones are affected first.

Worth sending Support the audit log entry's rule name, execution date and the site URL. In our case a rule scoped to a deleted project kept firing on schedule, and they disabled it from the backend.