Unify and manage your data

Processing History in the Unstructured Data Studio

Learn how the Processing History panel helps you track the status and results of document workflows in Unstructured Data Studio.

The Processing History tab shows the complete log of all document processing jobs executed in the Unstructured Data Studio. Each job represents a workflow execution and includes key details such as job ID, status, priority, and execution time. The history view includes quick-access tools like Quick View and you can view the full audit details by clicking the Job ID.

You would use it to:

  • Track completed and failed jobs

  • Understand job-level performance and outcomes

  • Debug entity creation or missing documents

  • Investigate system behavior after scheduling or workflow execution

Here's a Processing History screenshot:

Monitor jobs in Processing history

You can review completed and failed jobs, and access job-level task logs in Unstructured Data Studio.

To monitor jobs:

  1. Select the Processing History option from the left navigation pane. Review the list of completed, failed, in progress, and pending jobs. You will also see a list jobs processed.

  2. In the Filters section of Processing History tab, select the Status and Workflow name to narrow results further.

  3. Select Apply to view the filtered job list.

  4. In the Processing jobs table, for a job ID, select Quick View to view a high-level summary of the job.

    View the creation time, priority, and processing duration. See the list of stages with timestamps and statuses. Close the dialog to return to the Processing History page.

  5. Select a job ID to view the full audit of the job.

    Review each task name and type. The Status column confirms whether extraction, transformation, and destination stages completed successfully. Select the arrow button in the Result field to view extracted or generated output. Use the Copy icon to copy the output.

You've now reviewed a complete job record and can confirm if it succeeded or failed, and which phase (if any) caused the issue. This enables faster troubleshooting and insight into unstructured document workflows.