Blueprint logs help you check whether an automation ran and what happened at each step. Use them after testing a new flow or when a team member reports that an expected action did not happen.
Find and inspect a run
-
Open the logs
From Blueprints, select Logs. Use the filters to narrow the list by Blueprint or status: Success, Failed or Skipped.
-
Choose the relevant run
Review the Blueprint name, trigger entity, record ID, start time, duration and number of steps. Select the row to open its execution details.
-
Read the step results
In the details, check each recorded step's type, status, message and duration. A condition message says whether its rules evaluated to True or False. Only steps that ran appear in the step details; an unselected branch does not run its actions.
-
Investigate failures
For a failed run, read the error shown with its status and identify the step that failed. Check that the selected trigger and condition values are correct, and that action settings such as recipients, channels or webhook details are still valid.
-
Retest a focused change
Make one change at a time, save the Blueprint, and cause the trigger again with a test record. Return to Logs and compare the new result before relying on the automation.
Check whether the run started at all. If there is no matching log, verify the Blueprint is active and that the record event matches its selected entity and event.
For more, see Blueprints.