All Activities Undispatched From A Crew Shift And Stuck Queued For Dispatch Indefinitely, MWM v2.3.0.x
(Doc ID 2358277.1)
Last updated on OCTOBER 23, 2021
Applies to:
Oracle Mobile Workforce Cloud Service - Version NA and laterOracle Utilities Mobile Workforce Management - Version 2.3.0.0.0 to 2.3.0.1.0 [Release 2.3]
Information in this document applies to any platform.
Symptoms
A Crew Shift was closed and Activities dispatched when a Standby Shift was started. At some point, all Activities were recalled from the device by the scheduler then, stuck in a Queued for Dispatch status indefinitely. The Assignments were never created, so it never attempted to push the Activities to the device. It looks like the Scheduler failed to process these Activities.
The workaround was to manually unassign and then reassign each order. Then they dispatched without issue.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |