> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/reference/process-development/process-instance-list.md). # Process Instance List The Process Instance List view shows executed and currently running Process Instances in a selected Agent Group. It is used to review execution history, inspect failed or running executions, and open individual Process Instances for detailed log analysis. ## Process Instance List view The Process Instance List view provides an overview of Process executions. Each row in the list represents one Process Instance, which is a single execution of a Process. The list can show instances for one Process or for multiple selected Processes, depending on how the view was opened. The view is commonly used when monitoring integrations, investigating failed executions, checking execution duration, or searching for specific business transactions using Promoted Values.

Process Instance List view with Process executions shown.

## Opening the Process Instance List view Process Instances can be opened from the Process list. For a single Process, select **Show Process instances** from the Process actions, or select values such as **Last execution** or **Instance counts per day** from the Process list. To view instances for multiple Processes at the same time, select the wanted Processes in the Process list, open **Actions**, and select **Show Process Instances**. This opens the Process Instance List view filtered to the selected Processes. Viewing multiple Processes together is useful when following the lifecycle of a business transaction, such as an order ID, customer ID, or message ID, across several Processes. ## Displayed information The Process Instance List view displays key information about each Process execution. The available columns can depend on the view configuration and the available execution data. ### Execution graph At the top of the Process Instance List view, an area chart displays the volume and outcome of Process executions over the selected time period. The chart shows running, failed and successful executions as separate colour-coded areas stacked over time, making it easy to spot spikes in failures or periods of unusually high or low execution volume at a glance. The graph reflects the active filter settings, so adjusting the time range or state filters also updates what the graph displays. This makes it useful for identifying patterns, such as recurring failure peaks at certain times of day or gaps in expected execution activity. ### Instance details Below the graph is the list of Process Instances. Each Process Instance row can include details such as the Process Instance ID, Process version, start time, end time, duration, and username. These values help identify when the Process was executed, which version was used, how long the execution took, and which user or mechanism started it. Selecting a Process Instance opens the Instance view for that execution. The Instance view shows the Process flow and the logged execution data for each shape, depending on the configured logging level. ### Promoted Values Promoted Values can be shown directly in the Process Instance List view. They are values selected during Process development to make important execution data visible and searchable in monitoring views. Promoted Values are useful for business identifiers and operational values, such as order IDs, customer IDs, tracking numbers, message IDs, or error codes. They are logged even when the general log level is reduced, which makes them reliable for searching and filtering Process Instances. Large payloads should not be used as Promoted Values, because Promoted Values are always logged and can increase logging overhead. ## Filtering and search The Process Instance List view includes filters for narrowing down the shown executions. Filtering is especially useful in Environments with frequent Process executions. ### Time period The time period filter limits the list to Process Instances executed within the selected time range. This is typically the first filter to use when investigating an issue that occurred at a known time. In addition to the numerical input fields, the time period can also be selected by clicking and dragging on the execution graph. ### Instance state The state filter limits the list by Process Instance status. Common states include running executions, successful or finished executions, and failed executions. Depending on the view and available options, the state filter can also include more specific options, such as failed instances that have not been acknowledged. ### Search The search field can be used to search execution results and Promoted Values. SQL wildcards are supported, which makes it possible to search for partial values when the exact value is not known. For example, searching with a partial order identifier can help locate all Process Instances related to a specific business transaction. ### Auto refresh The list is automatically refreshed by default so that running and recently completed Process Instances are shown close to real time. Auto refresh can be turned off when there are many active executions or when you want to keep the current results visible while investigating earlier Process Instances. ## Process actions The **Process actions** menu in the Process Instance List view provides actions that apply to the Process itself rather than to individual instances. The available actions are **Run once**, **Activate**, **Deactivate**, **Log settings**, and **Edit**.

Process actions available in Process Instance List view.

### Run once The **Run once** action executes the Process immediately with a manually provided input. The execution is logged as a Process Instance and is useful for testing or for manually triggering a Process outside of its normal schedule or Trigger. ### Activate The **Activate** action enables the Triggers defined on the Process for the currently selected Agent Group. Activating the Process allows its Triggers to start executions automatically. ### Deactivate The **Deactivate** action disables the Triggers defined on the Process for the currently selected Agent Group. Deactivating the Process prevents new executions from being triggered automatically. Executions that are already running are not affected. ### Log settings The **Log settings** action opens the log level configuration for the Process. Log settings let you adjust how much execution data is captured for Process Instances, and can be configured separately for each Process, overriding the Agent Group-wide default. ### Edit The **Edit** action opens the Process in the Process Editor. All edits to a Process must be made in the Development Environment. ## Process Instance actions Actions for Process Instances are available from the **Instance actions** menu in the Process Instance List view. The menu can include actions such as **Acknowledge all errors**, **Delete all finished**, **Delete all successful**, **Save all as .csv**, **Acknowledge error**, **Comment**, **Delete**, **Resume**, **Save selected as .csv**, and **Terminate**. The exact available actions depend on the selected Process Instances, their states, and the user’s permissions.

Process Instance actions.

### Acknowledge all errors The **Acknowledge all errors** action acknowledges all failed Process Instances in the current list context. This can be used when the failed instances have been reviewed and no longer need to appear as unacknowledged errors. The action applies broadly to the relevant failed instances in the current view, so it should be used only when the visible or filtered set of errors has been intentionally reviewed. ### Delete all finished The **Delete all finished** action removes finished Process Instances from the current list context. Finished instances include Process Instances that have completed execution and are no longer running. This action is intended for cleaning up execution history. It should be used with care, because deleted Process Instance logs are no longer available for later analysis. ### Delete all successful The **Delete all successful** action removes successful Process Instances from the current list context. This can be used to clean up successful execution history while keeping failed or otherwise relevant instances available for investigation. As with other delete actions, the deleted Process Instance logs are removed from the monitoring view and cannot be used later for analysis. ### Save all as .csv The **Save all as .csv** action exports the Process Instances currently shown in the list to a CSV file. The export can be used for reporting, offline analysis, or sharing selected monitoring data with other teams. The exported data reflects the list context, such as the selected Process or Processes and the applied filters. ### Acknowledge error The **Acknowledge error** action is used for selected failed Process Instances. Acknowledging an error marks the failed instance as reviewed, which helps separate already handled failures from new failures that still require attention. When acknowledging an error, a reason can be provided. This is useful for recording why the failure no longer requires action, or how it was handled outside the Process execution. ### Comment The **Comment** action adds a comment to one or more selected Process Instances. Comments can be used to record investigation notes, operational decisions, or other context related to the execution. This is useful when several users are monitoring the same Environment, as the comment helps communicate whether an instance has already been reviewed or why a certain action was taken. ### Delete The **Delete** action removes the selected Process Instance from the list. Deleting an instance removes its logged execution data from the monitoring view. A confirmation is required before deleting a Process Instance. This helps prevent accidental deletion of execution history that may still be needed for monitoring, auditing, or investigation. ### Resume The **Resume** action is used for a paused Process Instance. A paused instance can be resumed when the Process has reached a checkpoint and is waiting to continue. The action is only available when the selected Process Instance is in a state that supports resuming. If the selected instance cannot be resumed, the action is disabled in the menu. ### Save selected as .csv The **Save selected as .csv** action exports only the selected Process Instances to a CSV file. This is useful when you want to share or analyze a smaller set of executions without exporting the full filtered list. Before using the action, select the relevant Process Instance rows in the list. ### Terminate The **Terminate** action is used for a Process Instance that is still running or otherwise active. Terminating an instance stops the execution and records the instance as failed. Termination is typically used when an execution is stuck, no longer needed, or waiting in a long-running state that should not continue. For long-running operations, the Process implementation should support cancellation where applicable, for example by using the available cancellation token in custom logic. If cancellation token is not used, for example in a Custom Task or in a Code Task with long iteration, the execution will remain stuck until marked as zombie, or until the Agent is restarted. ## Opening the Instance view Selecting a Process Instance opens the Instance view. The Instance view presents the executed Process visually and shows what happened during the execution shape by shape. For each executed shape, the view can show information such as the start time, duration, executed Task or Expression, and result. If extended logging is enabled, input parameters can also be visible. For API and HTTP executions, the logged details can include response information such as duration, response body, and headers when these values are logged.

Process Instance view of a Process execution.

The Instance view is similar to the Process Editor visually, but it is used for monitoring and analysis instead of editing. It helps identify where an execution succeeded, failed, or spent time during processing. ## Permissions and visibility The actions visible in the Process Instance List view depend on user permissions. If a user cannot see or perform an action, such as acknowledging an error or deleting Process Instances, the required Process Instance permissions may be missing. The available actions can also depend on the state of the Process Instance. For example, actions for stopping an execution are only relevant for active or running instances, acknowledging an error is relevant for failed instances, and resuming is relevant for paused instances. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.frends.com/reference/process-development/process-instance-list.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.