Use the activity log to help you see what is happening in your pipelines and to start troubleshooting.
Open activity logs
The different ways to view activity logs include:
- All pipelines—From the My pipelines page, select Activity log.
- Specific pipeline—From the My pipelines page, open the menu for a pipeline, and then select View activity.
Read activity logs
When a pipeline runs, details display about the actions and runtime. If there were errors when the pipeline ran, you can view details of the error and the step. Activity displays for pipelines within the last 90 days
Quick start triggers initiate more quickly than standard triggers, and include pipelines that:
- Have up to 4 steps
- Trigger a few times per minute from human action
- Operate on less than 100KB of data.
In the activity log, these triggers have an icon next to the trigger event name.
Here's an example of what displays when you open the activity for a single pipeline:
- Activity for the pipeline finishing running. Activity is automatically sorted with the most recent activity first. This type of activity also has an output, so you can see the result of the pipeline running.
- Activity for an upsert. There was an error when this action ran.
- Details of the error. Use these details to troubleshoot your issue.
- Information about the action that includes things like the type, channel, index, and step.
- Additional information available for this action. Expand these sections to learn more about things like what data the step used as an input.
- Activity for a pipeline that is still running, but has reached the limit for events available in real-time. Once the pipeline has finished running, the number of events that exceeded the limit is displayed. Learn more about limits.
The text in the log is colored. The colors indicate what the data type is. The colors and data types include:
- Red—boolean data
- Blue—numeric data
- Green—string
- Black—object, null, or undefined
Limits
- Activity logs are stored for 90 days.
- A limit of 10,000 events per hour for each pipeline step are available in real-time. This excludes critical events (triggered, finished, errors, throttling, and retries) which are always available in real-time. Non-critical events (loop-target, branch, and nested actions) that exceed this limit are available after 24 hours.