Source

Execution, error handling & monitoring — found from sitemap — Tray.ai

Checked for Tray.ai on 13 Oct 2026

Page: https://tray.ai/documentation/platform/automation-integration/building-workflows/configuring-steps/error-handling
Checked: 13 Oct 2026, 17:24 UTC
How we may use it: Public page, crawling permitted

Technical details

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

Cited by

Call connector endpoint 200 outcome field Report an error

“When calling operations using the Call connector endpoint, even though your payload may have passed Tray's input schema validation, you may encounter errors returned by the 3rd party. Therefore a 200 response does not necessarily indicate success from 3rd party. A 200 response will contain an outcome and a output field.”
Outcome success meaning Report an error

“If outcome is success, that means 3rd party service gave a successful response. If outcome is error, that means 3rd party service gave an error response. In either case, the response from the 3rd party can be obtained from output field.”
Form builder demo app testing Report an error

“It is highly recommended that you make use of our Form Builder demo app to test out the connector operations you will be making use of in your integration.”
Form builder capabilities Report an error

“This app allows you to: Send live calls to the 3rd party in question Inspect the input payload as it is constructed Inspect the success or failure responses from the 3rd party Edit the input payload in order to force and inspect errors”
UI form tutorial Report an error

“If you follow best practices in terms of programmatically working with our schema, as outlined in our Building a UI form tutorial you should be able to avoid errors with these idiosyncracies.”

1 fact read from this page is not shown because it could not be confirmed on the page as captured.