Postman Collection Runner Stops or Fails Midway

How to fix it

Try these in order — the most common fix is first.

1. 1. Let the run continue after errors

   1. In the runner's advanced settings clear 'Stop run if an error occurs'
   Did this fix it? Yes No

2. 2. Read the error badge

   1. NETWORK means connection/TLS, REQUEST means the request could not be built, SCRIPT means a pre-request or test script exception; Failed means a test assertion did not pass
   Did this fix it? Yes No

3. 3. Free memory

   1. Deselect 'Persist responses for a session', select 'Turn off logs during run', use the desktop app, or split the collection
   Did this fix it? Yes No

4. 4. Retry

   1. Click Retry Run, or run via Postman CLI for large jobs
   Did this fix it? Yes No

Symptoms

The runner halts after the first failing request, shows NETWORK/REQUEST/SCRIPT errors, or loses earlier responses on a big run.

Why it happens

• 'Stop run if an error occurs' enabled by default
• Script exceptions or request errors
• TLS handshake failures or timeouts
• Out of memory on long runs

This guide also covers

• postman collection runner stops
• postman runner not running all requests
• postman run stops on error

Other Postman errors

• Postman Could Not Get Response Error
• Postman Error: connect ECONNREFUSED
• Postman SSL Error: Self Signed Certificate
• Postman CORS Error in Web App
• Postman Scratch Pad Removed: Login Required to Save
• Postman Collection Runner Limit: You've Exhausted All Available Runs
• Postman Collections Not Syncing
• Postman Lost My Collections