Stop retrying on Schedule deletion when open incidents are untraceable #714
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When an Escalation Policy using and Schedule receives a new Incident, a snapshot of the EP gets created to trace the relation of the Incident with that EP and its dependencies during the Incident life cycle, however when a that Schedule gets moved from the EP before closing or reassigning the Incident, the traceability of the Schedule with the Incident is lost, therefore retrying on error "[Schedule can't be deleted if it's being used by an escalation policy snapshot with open incidents]" becomes meaningless, so this update is meant to return immediately after matching this scenario.
Test results