Getting 403 when creating opsgenie incident but incident is still created

[Jin Budelmann]

I am setting up a datadog workflow to create opsgenie incidents and I am using the Create Incident action. It fails with a 403 error but still actually creates the incident with all the correct information. I want to use the result of this in a subsequent step so need this to succeed. Is this a opsgenie bug or a config issue somewhere?

[Mubeen Mohammed]

Hello @Jin Budelmann 

Thank you for contacting the Atlassian Community. This is Mubeen.

The issue you noticed with the 403 error may only be possible with Insufficient permissions. There are no known issues with Opsgenie incident creation that can result in these errors with no impact on incident creation.

This may be possible if you have a custom script that involves Incident creation and follow-up script options that result in 403 errors. It is recommended that you verify the API key you are using and make sure it has the required permissions(Try with a Global API integration key with all the permissions enabled). 

After the API key verification also, if you continue to experience the same behaviour, then please open a support ticket with us at https://support.atlassian.com/contact/ explaining the Incident creation flow you are currently using so we can further validate this with your account details.

I hope the details provided are helpful. 

Regards

Mubeen Mohammed

Cloud Support Engineer