Monitor and manage workflow processes
To monitor and manage processes, you must locate the process, evaluate the status, and perform any actions necessary to address problems.
Monitoring background workflows
Background workflows generate System Job records to track their status. You can access information about these system jobs in several places within the application:
Settings > System Jobs
This will include all types of system jobs. You will need to filter records to those where System Job Type is Workflow.
From the Workflow Process
Open the background workflow definition and go to the Process Session tab. This will show only the system jobs for this background workflow.
From the record
You can edit the entity form so that the navigation will include the Background Processes relationship. This will show all the system jobs that have been started in the context of the record.
If an asynchronous system job (workflow) fails several times consecutively, the system starts to postpone execution of that job for longer and longer time intervals so that the administrator or app maker can investigate and resolve the issue. Once the job starts succeeding again, it will resume executing normally.
Actions on running background workflows
While a background workflow is running, you have options to Cancel, Pause, or Postpone the workflow. If you have previously paused a workflow, you can Resume it.
Monitoring real-time workflows and actions
Real-time workflows and actions do not use System Job records because they occur immediately. Any errors that occur will be displayed to the user in the application with the heading Business Process Error.
There is no log for successful operations. You can enable logging for errors by checking the Keep Logs for workflow jobs that encountered errors option in the Workflow Log Retention area at the bottom of the Administration tab for the process.
To view the log of errors for a specific process, open the real-time workflow or action definition and go to the Process Session tab. This will only show any errors logged for this process.
If you want a view of all the errors for any process, go to Advanced Find and create a view showing errors on the process session entity.
Status of workflow processes
When you view a list of workflow processes, any individual process can have one of the following State and Status Reason values:
|Ready||Waiting for Resources|
Deleting process log records
If your organization uses background workflows or business process flows that run frequently, the amount of process log records can become large enough to cause performance issues as well as consume significant amounts of storage. To delete process log records not removed sufficiently by one of the standard bulk record deletion jobs you can use the bulk delete system jobs feature to create a custom bulk record deletion job.
- Go to Settings > Data Management > Bulk Record Deletion.
- From the Bulk Record Deletion area, select New.
- On the Bulk Deletion Wizard start page, select Next.
- In the Look for list, select System Jobs.
- The following conditions are used to create a bulk record deletion job to delete process log records.
- System Job Type Equals Workflow. This targets workflow records.
- Status Equals Completed. Only completed workflows are valid to run the job against.
- Status Reason Equals Succeeded. Delete successful, canceled, and failed jobs.
- Completed On Older than X Days 30. Use the Completed On field to only delete workflow process log records that are older than 30 days.
- Click Next.
- Set the frequency that your bulk delete job will run. You can schedule your job to run at set intervals or create a one-time bulk deletion job Using the immediately option. In this example, a recurring job is set to run on May 21, 2018 and every 30 days thereafter.
Using the immediately option
Notice that you have the option of performing an immediate synchronous bulk delete of the records by selecting the Immediately option. This delete is performed with direct SQL Server execution rather than passing each record through the delete event pipeline, which can reduce the impact to system performance. This is a good option if you want to quickly clean up the extra workflow records instead of the bulk delete job waiting in the asynchronous queue for processing.
The Immediately option is enabled when the following conditions are true:
- Bulk delete job is for the System Jobs entity.
- The search criteria has the condition system job type equals workflow.
- The user creating the bulk delete job has global depth for the delete privilege on the AsyncOperation entity. The system administrator security role has this privilege.
The synchronous bulk delete will only delete AsyncOperation records in the completed state. A maximum of one million records are processed for each invocation. You will need to execute the job multiple times if your environment has more than one million records to remove.
Send feedback about: