when we try to extend the end date, future instances go into an 'aborted' status causing issue
Summary:
We have observe that when we extend the schedule end date of a schedule, future instances that were previously active go into an "aborted" status. Subsequently, even when you reactivate the schedule, newly created instances aren't executing as per the schedule.
Any suggestions?
Content (please ensure you mask any confidential information):
Version (include the version you are using, if applicable):
Code Snippet (add any code snippets that support your topic, if applicable):
Tagged:
1