Mobile Workflow Exception Handling

Describes how to handle a blocked mobile workflow.

If a mobile workflow is not received or processed on a device, this may indicate the mobile workflow is blocked in the message queue. By default, Unwired Server retries actions that threw recoverable exceptions every 15 minutes and it retries actions that threw unrecoverable exceptions every 3 days. Both types will continue to retry indefinitely, unless the administrator intervenes, either by fixing the error or by unblocking the mobile workflow in the Sybase Control Center queue.

This typically indicates that a workflow operation failed with a recoverable or unrecoverable error. To resolve the situation:

Check the Unwired Server and mobile workflow client trace logs for information.
- Unwired Server logs:
  - Aggregated Unwired Server logs – <UnwiredPlatform_InstallDir>\UnwiredPlatform\Servers\UnwiredServer\logs
  - Messaging service log details – <UnwiredPlatform_InstallDir>\UnwiredPlatform\Servers\MessagingServer\Data\Log
    
    <UnwiredPlatform_InstallDir>\UnwiredPlatform\Servers\MessagingServer\Trace
- Workflow client trace logs:
  - Single node – <UnwiredPlantform_InstallerDir>\UnwiredPlatform\Servers\MessagingServer\Data\ClientTrace
  - Cluster CDB node – <UnwiredPlantform_InstallerDir>\Data\Messaging\ClientTrace
Use information in the logs to resolve the problem.
Use Sybase Control Center to check message queue status, and to suspend, resume, unblock, or remove items in the queue. See:

Sybase Control Center for Sybase Unwired Platform > Manage > Managing Unwired Platform > Routine System Maintenance Tasks > Checking System Status > Checking Mobile Workflow Users and Queues