Environment variable issues

App and Docker Services use the Variables tab

Database Services expose connection details differently; see Database services under Services in the sidebar if you are editing the wrong place.

I saved variables but the app still sees old values

1. Save on the Variables tab, then run Deploy or Redeploy so runtime picks up changes (Environment variables under Deployments and Operations in the sidebar).
2. Wait for the Deployment to succeed; partial failures leave old processes running.
3. Confirm you edited the correct Service in the correct Environment.

Reference or secret syntax errors

1. Review allowed patterns in Service settings under Services in the sidebar (static values, references to other Services, secret(), combined strings).
2. A typo in a reference key prevents resolution; compare names to the target Service as shown in the UI.
3. Never paste real secrets into chat, tickets, or screenshots.

Variable “works locally” but not in dFlow

1. Compare Environment names: staging and production Services are isolated.
2. Check Worker Node timezone or locale only if your app depends on them (rare; usually code or config).
3. Database URL variables: use the internal connection values dFlow provides for co-located Services, not a laptop-only host.

Import from .env went wrong

1. If you used Import .env file, open each row and remove accidental quotes, spaces in keys, or duplicate keys. Save and Redeploy.

Related

• Service settings
• Environment variables
• Deployment issues