dFlow support and dashboard

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 in

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 support

• 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).

• Migration issues after Migrate from legacy Projects to Applications under Migration and Release Notes in the sidebar when behaviour still looks wrong after following the guide.

dFlow Cloud vs self-hosted

• dFlow Cloud: support scope and response expectations are summarised under Cloud limits and expectations under dFlow Cloud in the sidebar.

• Self-hosted control plane: you operate the stack; use Self-hosting troubleshooting under Self-Hosting dFlow in the sidebar for install and upgrade problems. Commercial support channels may still apply to your subscription tier.

What slows tickets down

• 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).

Related

• Troubleshooting overview

• Logs and debugging

• Documentation migration notes (canonical docs location)