If the workflow explorer does not respond
| Symptom | What to check |
|---|---|
| Workflow tabs do not change | The explorer uses first-party JavaScript. Check whether a browser extension or policy blocks it, then reload. |
| Copy reports unavailable | Clipboard access may be denied by the browser. Select and copy the visible sample text manually. |
| An expected page is missing | Check the path or use site search. Include the missing URL when reporting a broken link. |
If a contact or support request is uncertain
A form validation message identifies fields that need correction before submission. A network interruption is different: the browser may not know whether the server accepted the request. Retain any visible confirmation reference rather than treating the absence of an email as proof of failure.
After submission, keep the displayed reference for follow-up. No automated email confirmation is sent. Use the support contact page if you need to add context, and include the original reference so the messages can be connected.
Diagnose workflow failures by category
Choose a recovery path based on the affected boundary. An extraction mismatch, missing source, exhausted budget, and uncertain write need different responses. Preserve the operation identity whenever a system effect requires investigation.
- Input does not satisfy the contract: correct the source or choose a contract that explicitly supports it.
- A verifier finds a mismatch: inspect the stated rule and source references before deciding whether extraction, source data, or policy is wrong.
- A source is unavailable: distinguish missing evidence from evidence of an incorrect result.
- The budget is exhausted: do not assume another model attempt is authorized or that a previous system effect was absent.
- A write outcome is unknown: preserve the original operation identity and reconcile before attempting another mutation.
Send a useful issue report
For a website issue, include the page URL, what you expected, what happened, browser and device type, and the approximate time with your time zone. If the page showed a request reference, include it. A short sequence of reproduction steps is usually more useful than a broad description.
Remove credentials, private invoices, payment information, and personal records from examples. Report a suspected security issue through the security guidance rather than including exploit details or sensitive data in a general product inquiry.
Missing a detail or found a problem?
Send a documentation question →