When to contact support

dFlow docs and the dashboard are built to deflect repeat questions: try the Troubleshooting overview map first, then the specific symptom page (Deployment issues, Integration issues, and so on).

Before you write inCopy Anchor Link

1. Note Organisation, Application, Environment, and Service names exactly as shown.
2. Capture the time (with timezone) of the failure.
3. Attach or paste a sanitised log excerpt (remove secrets, tokens, passwords, personal data).
4. Say what you already tried (for example redeploy, DNS check, token refresh).

Good reasons to contact supportCopy Anchor Link

• You suspect a platform bug (others in the same region or org see the same error, reproducible steps).
• Billing disputes, tax or legal invoicing, or enterprise contract terms beyond self-serve pages (Billing issues).
• Security incidents: possible account compromise, abuse, or credential leaks (do not paste live secrets into tickets; rotate first when safe).
• Data loss or restore questions beyond documented backup flows (Backups under Deployments and Operations in the sidebar).

Support scope and plan expectations: Feature access and limits under Billing and Account.

What slows tickets downCopy Anchor Link

• Missing which Environment failed when you have many.
• Screenshots of logs that are unreadable; paste text when possible.
• Sharing production secrets in plain text (never required for triage).

RelatedCopy Anchor Link

• Troubleshooting overview
• Logs and debugging
• Documentation migration notes (canonical docs location)