Automations not working

Question

It seems that automations in jira are not working for my account.

All I get is:

Something went wrong

We encountered an unexpected error. Please try refreshing the page or contact support if the problem persists.

The request to load automation fails with HTTP 500

{

"timestamp": "2026-10-21T08:40:45.848+00:00",

"status": 500,

"error": "Internal Server Error",

"path": "/pro/rest/10111/pagecontext"

}

I tried accessing automations via Jira and also via Studio, the same problem on both sites.

I can't even contact support as it says Sorry, we can't find this Cloud URL. Despite the fact the URL is correct.

Alejandro Rodriguez (rza4trs) · Answer

Hello,

We are facing the same issue with a particular user. When an admin impersonates the user (grabs his identity from Admin console), he can see the Automation page and the manual triggers, but the user from his laptop can't.

We have cleared all cookies and browsing cache. In fact, we provided him Global Admin settings, but he still get the same 500 Internal Server Error in /pagecontext when accessing automations.

Also, we have checked with users that have the same permissions and that sit on the same exact network (to discard firewall issues), and the problem seems only apply to the affected user.

I am posting just for your knowledge, as I followed the aforementioned solutions but nothing works.

I am raising a support request and once I solve it I will post how. I just wanted to write down here as I see the same incident in less than 15-day period may be something worst that Atlassian have not noticed.

Cheers!

Christos Markoulatos -Relational- · Answer

@Arkadiusz Wroblewski thanks, didn't know about that one, good to have it on the radar. Only thing that makes me hesitate is the code: 403 is "not allowed", 500 is "something broke on their side". Could still be related, let's see what Ladislav comes back with.

@Ladislav Račák can you check two things? Does the automation page open for anyone else on your site, and what plan are you on? That second one is probably your support form problem too. The form only takes the URL from an admin or billing/technical contact, and on Free there is no technical support at all, only the Community. If you're an admin on a paid plan and it still says it can't find the URL, get whoever is the billing contact to add you as technical contact, or have them raise it.

Arkadiusz Wroblewski · Answer

Hi @Christos Markoulatos -Relational-

Atlassian has a similar issue with automation permissions, but instead of hitting a server error (HTTP 500), it shows as a forbidden error (HTTP 403).

https://jira.atlassian.com/browse/AUTO-1022

Regarding "Cloud URL not found", this can also happen when you're not signed in with an account authorized to raise support requests for that site.

https://community.atlassian.com/forums/discussion/3213991/cloud-url-for-support-requests-not-found

Best,

Arek🤠🧙‍♂️