View scheduled collection runs in Postman

Postman can run your collections on a schedule at specific times each day or week. For example, you may want to run a collection that tests your API every day. Use the Collection Runner to schedule collections to run automatically at specified dates and times.

To view scheduled collection runs in Postman, select a collection in the sidebar and select the Runs > Scheduled tab. To view the results of a scheduled collection run, hover over the run and select View.

Scheduled collection runs in team workspaces are visible to all members of the workspace.

Scheduled collection run summary

Use the graph to understand the health of your APIs over time. Each bar in the graph represents a collection run.

The upper section shows the average response time for each scheduled collection run. The lower section shows the number of failed tests for each run across all regions. To view the exact values for failed percentage and response time, hover over a run.

A red bar indicates that tests failed or errors occurred during the run. For more information, view the Console log.

Filters

Use filters to identify recurring patterns in your scheduled collection runs by selecting particular run types and results.

Select Clear Filters to return to your original dashboard view.

Filter by type

Filter by run type to compare how response times changed between all runs, manual runs, and scheduled runs. Select the Type dropdown list, then select the type of run to view.

Manual runs are initiated in Postman. Scheduled runs are initiated by the schedule you set when creating or editing your scheduled run. Webhook runs are initiated by integrations you've created.

Filter by run result

Each scheduled run is labeled based on its result:

• Successful - The scheduled collection run finished with no issues and passed all tests.
• Failure - The scheduled collection run finished; however, one or more tests failed.
• Error - The scheduled collection run was unable to complete due to an error. An error can occur if there is a syntax error in the test code, a network error, or for various other reasons. If you get an error, the Console log can help you identify what caused it.

• Abort - The scheduled collection run timed out because it didn't complete within the allotted 10 minutes (Postman Free plans) or 15 minutes (Postman paid plans).

Filter by run result to compare how runs with the same result differ. Select the Run result dropdown list, then select one or more types of run results to view.

Time traverse

Review past run results to understand what happened at a particular point in time. To go to a specific point in time, select Go to on the graph, select a time and date, and select Apply.

To revert the view to the most recent runs, select the time and date on the graph, then select Reset.

Test results

To get more details about the tests for a scheduled run, select a bar in the graph, then select Test Results below the graph. Details include the passed or failed tests, the response codes, and the response times.

Console log

The Console log shows details about a scheduled run along with any log statements from your pre-request and post-response scripts. Use the log to troubleshoot issues and learn more about a run's behavior. To view the log for a scheduled run, select a bar in the graph, then select Console Log below the graph.

Log details include the stages of a collection run, such as preparing run, running, and run complete. The log also shows any errors and test failures. Selecting a request in the Console log will open it in a new tab, so you can review and edit the request as needed.

Scheduled collection run logs are retained for a period of six months. If you select a scheduled collection run that's outside the retention period, you can view the number of failed tests and errors. Other collection run details will no longer be available. To request this information, contact Postman support.