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

Opsgenie delayed incomingData?

Hi, I have a service ticket open, but wanted to ask the community if they have had this issue occur?

Use Case: we have an Opsgenie to JSM integration per the documentation enabled.

Symption:  Occasionally all comments and actions to close an issue from Opsgenie are successful, but sometimes we get 404 errors.

In the logs, I'm seeing these "Discarding delayedincomingData, expired because alert does not exist" But the alert definitely exists but it is closed in Opsgenie and open in JSM. 

I have no idea what are why these are occurring. 

Any ideas? Screen Shot 2021-03-25 at 4.46.25 PM.pngScreen Shot 2021-03-25 at 1.02.03 PM.pngScreen Shot 2021-03-25 at 9.42.56 AM.pngScreen Shot 2021-03-25 at 8.22.36 AM.pngScreen Shot 2021-03-25 at 8.16.58 AM.pngScreen Shot 2021-03-25 at 8.16.48 AM.png

1 answer

1 vote
Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 29, 2021

Hi @Chris ,

We covered the 404 error in your other Community post here:


As for the "Discarding delayed incomingData, expired because alert does not exist" log - we determined this occurred because there wasn't an open existing Opsgenie alert in your account when that request was made, and the alert was closed before the request was made.


Hope all of this helps! Let us know if you run into any other questions or issues.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events