Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Statuspage Web Request Returns HTTP status 500 Response

Hello, I'm using the Statuspage api to create incidents in Statuspage using a Jira workflow.  On certain Jira transitions, Jira automation sends the web request to statuspage.  When testing outside of Jira (using powershell), there are no issues.  When using the workflow/automation, the very first time it runs, I get an "HTTP status 500" error response.  The next time I run it, using the same issue request or new one, the automation succeeds, and any subsequent web requests succeed.  Can anyone help me in understanding why the first call fails?  It seems to be time dependent.  After the first failure, all works as expected right after.  But, if I walk away and try again 30 minutes later, the first web request fails again, and any subsequent attempts work fine.  See attached print screens for the error and the "create incident" web request.

500 Error to Statuspage.pngCreate incident web request.png

2 answers

1 accepted

2 votes
Answer accepted

Circling back after this issue has been resolved.  The problem had to do with our configuration of the load balancer with our Jira dev environment, which only runs on one node.  The issue does not persist in prod.

Thanks for the help,


That is great to hear Eric! Thanks for letting the community know :) 

1 vote

Hi Eric,

That issue is quite interesting! I did look and found a similar issue being reported in this community post

It looks like this user resolved it by changing the format of the JSON, but that does not seem to be the case here.

I would recommend setting up a webhook to also post the payload out to a site like this will allow you to see if the non-statuspage endpoint received the payload and without issues. This will also help verify the payloads between the send-offs are the same. 

I hope this helps get you in the right direction. Additionally, if this comes down to an issue with Automation for Jira we will need to get that reported to the appropriate team. 

Opening up a ticket to the Statuspage support product at will assist us in collecting all needed information for this. 

Thanks so much 

Hi Chris,

Thanks for the recommendations.  Using I verified the payload was sent/received using Jira Automation each time without issue, while Statuspage is still returning a 500 error on the first POST, then succeeding on subsequent POSTs.  I tested again with powershell as well, and all POSTs succeeded with no issues.  It seems the issue may be with Jira Automation.  I've opened a ticket via (SPSP-21223).


Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Statuspage

New feature: Slack notifications for Statuspage

We're excited to announce the release of a long-requested feature on Statuspage. Now visitors to your status page can subscribe to get notified in Slack when you report an incident or maintenance. Th...

3,078 views 8 20
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you