Select the History tab to see information about the processes you have run in SS&C | Blue Prism® Desktop. A list of historical processes displays, in date/time order, starting with the most recent. Each entry in the list is one session, and represents a single run of a process. Initially your 10 most recently run processes are listed, and more are loaded as you scroll down. The amount of history available to you depends on the data retention policies in place for Desktop session management at your organization. For example, you might be able to see all the sessions you have ever run, or the list might be limited to a fixed time period, such as the last six months.
The following information and options are available:
Process name – The name of the process run in the session.
Completed at – The time and date this process finished running. This only displays if the process ran successfully.
Scroll bar – A scroll bar displays when there are more records that can fit on screen. As you scroll down, more historical sessions are loaded into the list in date order.
Started at – The time and date this process started running. This only displays if the process did not complete running.
Not completed – Indicates that this process failed to complete. There are various reasons why this might happen, for example, if the process was manually stopped, or invalid data was entered.
View issues – Opens a new screen displaying more information about why the process failed to run correctly.
View parameters – Opens a new screen displaying the values you entered for start-up parameters. Only start-up parameters will display on this screen. If you provided mid-process inputs during the session, these do not display.
Back to top – Returns you to the first entry in the list.
View issues
If a process does not successfully complete, you can see more information about why it failed by clicking the View issues link. The name of the process and its start time display, followed by a message that explains why it failed.
In this example, you can see that the user manually stopped the process while it was running, by clicking Stop the process.
If you need help to fix the problem, you should give this information to your system administrator. They are able to view a complete session log with more detailed information about all the processes that you have run, any additional information you entered, and details of why a process failed.
Docs
