dFlow surfaces several log types. Pick the one that matches when the problem appears.

Build and deploy logs

Use when: the Deployment never succeeds, the build step fails, or the image cannot be prepared.

Where: Application → Environment → Service → Deployments; open a deployment and use the log action the UI provides (wording may be View logs or similar).

Tip: The first compiler or package manager error is usually the root cause; scroll up from the last line.

Runtime logs

Use when: the Service is running but returns errors, restarts, or behaves incorrectly under traffic.

Where: the Logs tab on the Service while it is active. Streams may truncate; reproduce once and capture promptly for transient bugs.

Worker Node (server) logs

Use when: operations that touch the node fail (plugin actions, disk, SSH execution), or multiple Services on the same node misbehave.

Where: Server logs (or equivalent) in the dashboard for the Worker Node. Pair with Compute and worker node issues.

What to capture (for yourself or support)

1. Organisation name, Application name, Environment name, Service name (as shown in the UI).
2. Approximate time (with timezone) of the failed Deployment or error.
3. A snippet of the log around the first clear error (redact tokens, passwords, connection strings, and personal data).
4. Whether the Service is Git, Docker, or database type.

Task guide: Logs under Deployments and Operations in the sidebar.

If logs are empty or missing

1. Confirm you opened logs for the Service and Deployment that actually failed.
2. Retry once to reproduce; some failures clear quickly.
3. Check Compute and worker node issues when the node is unreachable.

Related

• Deployment issues
• Troubleshooting overview
• When to contact support