Issue Summary

When a user tries adding up to 100 individual responders to an incident, only some users (20 to 40) get responder alerts. This happens because of a limitation in the Opsgenie legacy code.

Task failed for jira/classic:workflow with message java.lang.NullPointerException... halting execution of workflow  

Expected Results

All the responders must get responder alerts successfully and at once.

Actual Results

Currently, if more than 20 individual responders are simultaneously added to the incident, the system will randomly fire alerts for only 20 responders. The rest of the responders will be added, but not notified, causing a potential gap depending on the use case.

Workaround

We found out that adding new responders after the first addition triggers the "update" mode for the Responders field and generates a new batch of 20 alerts for the previously added responders. Also, this bottleneck does not apply to responder teams.