Tasks Stuck In Queued For Dispatch After Assignment Canceled
(Doc ID 1950853.1)
Last updated on SEPTEMBER 22, 2022
Applies to:
Oracle Utilities Mobile Workforce Management - Version 2.0.1.5 to 2.1.0.6 [Release 2.0 to 2.1]Information in this document applies to any platform.
Symptoms
Bundled Task 1234 was in Dispatched state while 5678 encountered a problem and was stuck in Queued for Dispatch after assignment canceled. In the smauto log, this assignment is undispatched, and then another assignment is dispatched right away again. The new dispatched one is not picked up by MWM for some reason.
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 |