Every Process execution is recorded. The platform retains a history of each run, including when it started, who or what triggered it, what parameters were supplied, the outcome, and — depending on the logging level — a detailed log of what the Process loaded, calculated, and wrote.
Viewing execution history
There are two screens for reviewing past executions.
Process Execution screen — accessible from Processes \> Process Execution within the application. Select a Process from the upper panel to see its execution history in the lower panel. This screen is primarily for running Processes, but also gives a quick view of recent runs.
Process History screen — accessible from Processes \> Process History. This screen shows a full record of every Process that has run in the application, including queued jobs awaiting execution. Use the Filter to narrow results by date range, status, or other attributes. Select Detail to expand additional information about a specific run, including the Calculation Log link and the process information field that describes how the Process was triggered.
For each execution, the history shows: the Process name, start date and time, status, the parameters that were supplied, and the user or system that triggered the run. For completed executions, the end date and time and Calculation Log are also shown.
Execution status values
Status | Meaning |
Queued | The Process is waiting in the execution queue |
Running | The Process is currently executing |
Success | The Process completed and results were written to the database |
Warning | The Process completed with non-critical issues; results were still written |
Failed | The Process did not complete; no results were written |
Calculation Logs
A Calculation Log is generated after each Process execution. It captures what the Process loaded, calculated, and produced. The amount of detail in the log depends on the Logging Level set on the Process — see Create and Configure a Process for how to configure the logging level.
To access the Calculation Log, navigate to the Process History screen, locate the execution, and click the link in the Calculation Log column. The log downloads as a compressed file. Extract it and open index.html to navigate the contents.
What the log contains
The log package may include some or all of the following, depending on the logging level:
index.html — a summary of the execution sequence with timing information for each stage. Includes input parameters, record counts for each input and output, overall status, and links to associated workbooks.
Excel workbook — the Process Logic workbook as it was at the time of execution, populated with the actual input data and showing the calculated results. This is the most useful file for understanding what the Process did and diagnosing unexpected results. One workbook is included per Process in a chain.
Input XML (Verbose only) — the raw input data as XML.
Output XML (Verbose only) — the raw output data as XML.
No log files are generated if the Logging Level is set to Silent.
Reading the index.html timing entries
The index.html file records the time taken for each stage of execution. These entries are useful for diagnosing performance issues — for example, identifying whether time is being spent loading data, recalculating the workbook, or writing results to the database.
Log entry | Meaning |
Process initialised in | Time to process parameters and initialise execution |
Data loaded from database in | Time to load all input data |
Input written to calculation log in | Time to write input data to the log (Verbose only) |
Loaded spreadsheet in | Time to load the Process Logic workbook |
| Time to load each individual input into the workbook |
Input data loaded into spreadsheet in | Total time loading all inputs |
Spreadsheet recalculate completed in | Time for the workbook to recalculate |
Spreadsheet written to calculation log in | Time to write the recalculated workbook to the log |
| Time to extract and validate each output |
Results extracted from spreadsheet in | Total time extracting all outputs |
Output written to calculation log in | Time to write output data to the log (Verbose only) |
Rule executed in | Total elapsed time before writing to the database |
Stored x | Time to write each output to the database |
Results processed in | Total time writing all outputs to the database |
Process completed in | Total time for the entire execution |
If a Process is loading data slowly, the "Data loaded from database in" entry will be high — consider whether the Filter is selecting more records than needed. If recalculation is slow, the "Spreadsheet recalculate completed in" entry will be high — review the workbook for performance issues (see Process Logic Workbook).
A useful diagnostic pattern: if the log shows, for example, 50 objects loaded but only 40 stored, there may be an issue during the write phase. Review the output logic for that execution.
Notifications in the history
Below the execution records in the Process History screen, a Notifications section shows any Error, Warning, or Information notifications generated by the selected execution. These are the same notifications that appeared on the Process Execution screen when the Process ran. From here you can review the detail of each notification and close ones that have been actioned.
Version history for an execution
Changes to the status of a Process during its lifecycle are stored in an audit log. To view the version history for a specific execution, click the history icon next to that record in the Process Execution screen. The version history shows each status transition — for example, from Queued to Running to Success — with timestamps. The version number indicates the sequence, with 1 being the initial record.