Source

Execution, error handling & monitoring — found from sitemap — Zapier

Checked for Zapier on 13 Oct 2026

Technical details

type: page
http status: 200
content hash: sha256:e003af9fc6e974c82b02279e570ce9f04c55581c3adfc3fd40bc0d6efbb46eee
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

User notification Report an error

“This will display an error message to the user in their Zap history and they will be notified via email based on their notification settings.”
Monitoring page Report an error

“Monitor spikes in errors from the the Monitoring page in the Platform UI as leading indicators of problems users are facing within your integration.”
Custom error API Report an error

“Format the error to include a second, optional argument code machines can use to identify the type of error, and last, optional argument of a HTTP status code.”
Cli middleware Report an error

“Switching to the Platform CLI, allows you to make use of HTTP middleware to implement any custom error response handling.”
Skip throw for status Report an error

“In the UI, skipThrowForStatus is set from the Advanced tab. This allows for custom error handling for status codes above 400. Note that 401 status codes will throw a RefreshAuthError regardless.”
UI code mode Report an error

“Once set, you can add error handling when in Code Mode within the API Configuration for each trigger/action/search.”
Two error scenarios Report an error

“During the Zap setup process, stopping them from enabling and activating their workflows”
No success on error Report an error

“Even if the message included in the response details an error, users should never receive a success/200 response if there was an error in the request as this will not show up as an error in the Zap history.”

7 facts read from this page are not shown because they could not be confirmed on the page as captured.