Template troubleshooting
Common template messages and situations: skipped apps, environments, compute, drafts, publish errors, and access.
“N app service(s) skipped (unrecognized or missing git provider)”
What it means: One or more Git apps in the template were not included because each app must use GitHub, GitLab, Bitbucket, Azure DevOps, or Gitea.
What to do: Open Create template, set the Git host on every app, Save, then deploy again. Check the count of services on the template step.
“This template has no deployable services”
What it means: Nothing was left to deploy (for example every app was skipped and there are no databases or Docker services).
What to do: Add a database or Docker service, or fix the Git settings on apps.
No environments in the dropdown
What it means: Every Environment on that Application runs on compute where this deploy flow is not available (certain dFlow-managed setups are hidden here).
What to do: Create a new Environment on your worker or linked server, or pick another Application that already has one.
Environment selection cleared after a link
What it means: The link pointed at an environment that cannot be used here; the page reset the choice.
What to do: Pick a different environment or create a new one (see above).
Cannot pick a server (shows In use)
What it means: That server already belongs to another Environment.
What to do: Pick another server, add capacity, or change the other environment, following your team’s process.
“Finish application setup first” or “Finish environment setup first”
What it means: The Application or Environment is still draft.
What to do: Use the on-page buttons to complete setup. When the product supports it, you can return to Deploy from template afterward.
“Failed to load template” on Configure
What it means: The template did not load (network, access, or wrong catalogue tab for that template).
What to do: Click Try again. Make sure you chose Personal, Official, or Community to match where the template lives. Confirm you can still open Templates.
Continue greyed out on Configure
What it means: No services remain on the map.
What to do: Add a service back or reload the step.
Error about managed environments
What it means: This deploy cannot target that environment.
What to do: Same as No environments in the dropdown: use your own server or a new Environment.
“Template deployment is not available for dFlow-managed environments.”
What it means: The Environment you picked runs on dFlow-managed compute that does not allow this template deploy path (the check matches the managed restrictions logic in the product).
What to do: Create or use an Environment on your worker or linked Custom compute, then run Deploy from template again. Same idea as No eligible environments above.
Publish errors
| What you see | What to do |
|---|---|
| Short description too short | Add at least 10 characters in Short Description. |
| Template Overview too short | Add paragraphs in Template Overview until the plain text is at least 100 characters. |
| Name missing | Fill Name. |
Personal tab empty or error
What it means: Your role may not include viewing organisation templates.
What to do: Ask an admin. See Roles and permissions.
Delete greyed out
What it means: The template is still published to Community.
What to do: Unpublish, then Delete if you still need removal.
Application / Environment deploy fails
What it means: The deploy wizard is missing a required field (application, environment, or compute/server).
What to do: Fill every required field in Deploy from template, or create the Application / Environment first and retry.
Still stuck
- Open logs and Deployments for each Service.
- Deployment issues under Troubleshooting in the sidebar
- Integration issues under Troubleshooting in the sidebar for Git or registry problems