The Processing history view helps you see exactly what happened during each run – so you can investigate issues, validate system behavior, or just stay in control.
Point 1
Point 2
Point 3
etc.
A document can be processed by multiple schemes, each creating a separate instance. Within each instance, there may be several runs – either if this is defined by the scheme design or if the document has reappeared as a source object for the same scheme.
Since the data in the document may change between runs, the processing flow can differ even when using the same scheme.
To open the processing history, click the icon at the end of the instance row in the Document Processing table.
[ADD IMAGE]
Each run is saved as a session in the processing history.
Sessions are displayed from bottom to top and grouped by date, making it easy to track the sequence of processing attempts over a long period.
A session records the state of the document at the time of processing. Click the gray field to expand the details.
[ADD IMAGE]
Sessions (repeated runs of the object within the current instance) will continue as long as workflow conditions or project settings postpone processing. At the end of each session, you can see when the next run is scheduled.
If no further runs are expected, the status will be Completed.
Sessions consist of steps. Each step contains detailed information on how the session was executed.
[ADD IMAGE]
Steps consist of events. Each event is assigned a number.
Hover the mouse pointer over the end of a step row to see the hash icon (#), which displays the event number in a tooltip.
[ADD IMAGE]
This event number can be used in the Events in processing history condition, if the scheme needs to check for the presence of such a step in the history.
The bottom row displays the initial reason for launching the instance.
[ADD IMAGE]
Typical scenarios:
- Document received from the Unused tickets source
- Document launched manually
For more detailed viewing, change the category level:
- Info (default): shows only action blocks
- Trace: displays the full processing path, including condition evaluation
- Debug: provides additional technical information
- Fatal / Error / Warning: shows only steps containing warnings or errors
[ADD IMAGE]
If you need a more detailed view of the processing history, switch to the Trace level. It displays the full processing path of the PNR within the scheme – not only how each action was executed, but also how the system evaluated conditions during processing.
[ADD IMAGE]
Icons on the right side of the session row indicate important events that occurred during processing:
- Tag assigned
- E-mail sent
- Error / Warning
[ADD IMAGE]
Hover over or click an icon to view details.
In each session row, you can also navigate to more details:
- View web logs
- View scheme path in this particular session
[ADD IMAGE]
Logs follow a request–response format and show which data was requested, how it was requested, and what responses were received.
[ADD IMAGE]
A scheme opened from the processing history will look slightly different – it highlights only the steps that were actually executed during that processing run.
[ADD IMAGE]
The scheme displays a Processing history label in the top-left corner, along with the document number, scheme name, and the date and time of processing.
Hover over or double-click an element to see its configuration.
[ADD IMAGE]
A single click on an element will open an additional menu:
[ADD IMAGE]
- Question mark: quickly create a support ticket with a link to this step
- Link: copy link to the element
- Info icon (i): view detailed processing information, including which checks were performed
From here, you can edit your scheme or view its current version.
[ADD IMAGE]
Learn more: Canvas.
If you need support, hover over the row of the processing session in question to display a question mark icon. Clicking this icon opens a form you can fill out to contact our support team.
[ADD IMAGE]