Contact the DigLab onboarding or support contact named in your handoff. That contact can match the request to the correct organisation and connection. This public documentation site does not collect support messages or connection keys.
Before sending a request#
Check troubleshooting and identify the failing stage. If a write may already have completed, say so clearly and avoid repeating it until the state is checked.
Support request template#
Organisation or connection reference:
AI application and version:
When the problem happened including timezone:
Task I was trying to complete:
Stage that failed:
Tool name if known:
Error code and redacted error text:
Expected result:
Last known successful test:
Recent changes to device client or account:
Could a write already have completed:Safe evidence#
Use a small redacted screenshot or the relevant error text. Remove passwords, keys, authorisation headers, cookies, private customer records and unrelated account details. Inspect attachments and hidden content before sending them.
If support needs account authorisation, use the agreed secure route. Never paste a credential into the documentation search box, a public comment or an AI conversation.
Suspected exposure or wrong account#
Stop using the affected connection. Report the connection reference, what appeared wrong and when you noticed it. Avoid opening more records to investigate the extent yourself. DigLab can check the configuration and arrange the appropriate containment and verification.
Requesting a new capability#
Use request a custom integration and provide the business task, official service documentation and target account. A capability request is different from a failure in an already accepted workflow.