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 mobile workflow trace log, which is located in <UnwiredPlatform_InstallerDir>\UnwiredPlatform\Servers\UnwiredServer\logs\WorkflowClient, for information.
This log tracks incoming messages, either from the client or from DCN or e-mail notifications, what Sybase Unwired Platform calls get invoked as a result, what the output is from the Unwired server, and what message it is transformed into when a response is sent back to the client.
Check the Workflow client trace logs:
- 1. Log in to Sybase Control Center.
- 2. In the left pane, select Applications.
- 3. Select the application for which you want to view the trace logs and click Get Trace.
  The trace files are located in <UnwiredPlatform_InstallerDir>\UnwiredPlatform\Servers\UnwiredServer\logs\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 > Deploy > Mobile Workflow Packages > Configuring a Mobile Workflow Package > Checking Mobile Workflow Users and Queues.