Issue Summary

In short, it looks like when Opsgenie sends us a payload with a request to create an incident and update component statuses, we do it in a strange order. We first create the incident, and then we update component statuses. This leads to a confusing UI experience for Team Members, and could potentially an odd experience for API or Webhook users.

Steps to Reproduce

1. Configure the Opsgenie integration (https://docs.opsgenie.com/docs/statuspageio-integration) to "create an incident and update the components'/incident's statuses according to tags"

1. Create an Opsgenie alert that includes at least one of your pages components referenced as a Tag and set it to Major Outage, using their format of cmp_[component name]:[status] (e.g. cmp_Login:major_outage)

1. Login to your Statuspage account and go to the Incidents section - observe that the incident is opened, and the color matches the severity based on your component status choice

1. Click into the incident so you can see the full incident history

Expected Results

The first post to the incident shows your selected component, and the icon for it being in Major Outage

Actual Results

The first post to the incident shows your selected component, but with the Operational icon. As a Team Member, I may think that my incident did not properly process, and may post a new update that is not necessary.

If you check the activity log, you will see the order of events where we create the Incident first, and then process the component status change. If we could somehow swap the order, that would prevent confusion.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available