Versions Impacted: 3.2 through 3.3.7
Number of customer who have encountered issue: Three
Resolution Status: Resolved in version 3.3.8 and above
Description:
In rare instances a network order or events error can put the Scheduler in an invalid state with an empty, non-removable schedule blocking the queue.
Workaround:
This can be resolved by connecting to the tenant database (the one with the guid in the name) and executing two commands:
db.ScheduleInstance.remove({})
db.StepInstance.remove({})
Comments
0 comments
Please sign in to leave a comment.