Workflow Errors
The Design tab can assist you in understanding why a design failed, at what time it failed, and at what point in the workflow it failed. Further, the Design tab allows you to retry the errant task, which is particularly helpful if the failure was caused by a service being unavailable. Once the service is back up, you can retry the task, and the design picks up where it left off in the workflow.
Find Designs with Workflow Errors
There are two main ways to find designs with errors quickly:
-
Click the View Only Designs with Workflow Errors
button. As implied by its name, this winnows the list of designs down to those with errors.
TIP: This button is an on/off toggle. Click it to view only designs with errors, and click again to return to all designs. -
Use the Search field to find the errant design. See the help topic List of Designs to learn more about the Search field.
Diagnose the Error
After finding the design with a workflow error, the interface provides diagnostic information.
Here, you can view:
-
Message Type
-
Time of occurrence
-
Machine name
-
Exception Type
-
Exception Message
-
Stack Trace
-
Message Body
-
Advanced Details, which include:
-
DeadLetter DocID
-
Resource Type
-
SessionID
-
You can perform the following actions:
-
View Logs (this button is only visible if your company uses the Hosted Edge).
-
Click View Logs. This brings you to the Logs tab, with the log pre-filtered to the selected design.
-
-
Copy to Clipboard
-
Refresh
-
Cycle through Multiple Errors
-
Retry
-
Click Retry to send the errant task back through the workflow. This is particularly helpful if the failure was caused by a service being unavailable. Once the service is back up, you can retry the task, and the design picks up where it left off in the workflow.
-
-
ArcGIS Logs
-
When you click ArcGIS Logs, it opens ArcGIS Server Manager in a web browser. After you log in, it brings you directly to the View Logs dialog. There, you can query the logs based upon severity of the warning, age, and source of the message. This is helpful to view the issue from ArcGIS Server’s perspective, which might fill in additional details as to why something failed.
-