Skip to Content
Resources

Send a useful support request

Include the route, status, workspace context, and time of failure without sending credentials or customer data.

Resources
01

What to include

Send the request method and path, HTTP status, approximate time with timezone, workspace id, and the smallest safe description of the expected and observed behavior.

Remove bearer credentials, signing secrets, raw customer records, and private file contents. If a run is involved, include its run id so the team can locate the server record.

Email
support@trysupervisor.com
Status
Use /status for current incident information
Call
Use /book-a-call for implementation questions
02

Before sending

Confirm the key has not expired, the owner remains a workspace member, and the route uses the intended workspace id. Retry only when the response is transient or supplies a delay.