🎯 Summary

PIMS-2339

What I hope is the last addition to this ticket.
To account for the time differences in CHES (DEV seems to be fast to cancel, but TEST is slow), it will now try another three times if the first status request doesn't return cancelled. Hopefully this will resolve the race condition problem where their TEST server takes an additional second to actually cancel the notification behind the scenes.

Changes

• Added else statement that retries up to three times if the initial status request after cancelation isn't successful.

Testing

• Try to requeue a notification in the Pending status.

🔰 Checklist

• I have read and agree with the following checklist and am following the guidelines in our Code of Conduct document.

• I have performed a self-review of my code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation where required.
• I have tested my changes to the best of my ability.
• My changes generate no new warnings.