Impact of In-Memory Workflows on UI

Checking Progress in the Event Log

• An event is not generated when a workflow is run as in-memory. In this case, you cannot check event details for operations triggered by an in-memory workflow. However, if you have configured in-memory workflows that are persisted on success (for example, if you set the savestateonsucess property to true), and the event is generated, you can view the result in the Event Log after the workflow has finished executing.
• Intermediate event logs are available if the workflow contains the CheckpointWorkflow activity, async subflow, spawn workflow activity, or if the activity suspends. If a workflow errors out, the entire Event Log is available for debugging.
• If a data source upload or an import operation triggers an in-memory workflow, the Check Progress link (which you can use to track progress in case of regular workflows) redirects the event to an appropriate page with a message that the event is an in-memory operation.

Checking Progress of Records for Workflows Run In-Memory

If you add a record in-memory, you can check the success of the workflow by searching for the record in the catalog or checking the record count in the catalog.

Record history does not contain any reference to events processed in-memory. The link to the event is disabled and the event column shows a message in memory.