Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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,


Chris DeGidio
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 21, 2021

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

1 vote
Chris DeGidio
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 09, 2021

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
AUG Leaders

Atlassian Community Events