Unable To Unassign Queued For Dispatch Activities When Crew Shift Is Deleted
(Doc ID 2380870.1)
Last updated on MARCH 25, 2019
Applies to:Oracle Mobile Workforce Cloud Service - Version NA and later
Oracle Utilities Mobile Workforce Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 2.3]
Information in this document applies to any platform.
Activities were in a Queued for Dispatch status to a Crew Shift. That Crew Shift was deleted by a User. The Activities remaining permanently in a Queued for Dispatch status, stuck trying to dispatch to a Crew Shift that no longer exists. A Crew Shift deletion should be treated the same as canceling the Crew Shift, it should release all Activities currently assigned/queued to that Shift.
Instead, the Activities stayed Queued for Dispatch and created 2 To Dos for every Activity (about 30 Activities). A Task Monitor Error for the Shift ID not found and Scheduling Error for the same reason.
When attempting to manually unassign the Activity, we received an error "Resource restriction value xxxxxxxxxdx4063 invalid. Must be a valid shift for type M1DS - Excluded Shift". It's failing while trying to add the currently assigned invalid Shift as a restricted Shift to prevent the Activity from being reassigned.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!