Integrations let Services read repositories and images, and (on dFlow Cloud) connect provider accounts for infrastructure. Symptoms usually appear as build or pull errors; always capture Logs and debugging output.

Git: cannot list repos, clone fails, or webhook never fires

1. Reconnect the integration from organisation or account settings and accept any new provider permissions.
2. Confirm the token or GitHub App installation still has access to the organisation or repo (GitHub integration under Integrations in the sidebar, Git source integrations under Integrations in the sidebar).
3. Check branch name and default branch settings on the Service match the repo.
4. Automatic deploy on push depends on provider setup; verify webhooks in the Git host if pushes do not start builds.

Task guide: Connect your Git provider under dFlow Cloud in the sidebar.

Docker registry: pull denied or manifest unknown

1. Re-enter or rotate registry credentials (Docker registry integration under Integrations in the sidebar).
2. Confirm image name, tag, and registry host match what the Docker Service expects (Docker services under Services in the sidebar).
3. For rate limits, retry later or authenticate (provider dependent).

AWS or other cloud account errors

1. Review AWS integration under Integrations in the sidebar and Cloud provider accounts under Integrations in the sidebar for linking steps.
2. Check IAM or API permissions against Integration permissions and prerequisites under Integrations in the sidebar.

Narrow vs platform integration docs

This page is the customer troubleshooting entry. Deeper walkthroughs live under Integrations overview under Integrations in the sidebar and Integration troubleshooting under Integrations in the sidebar as those guides are expanded.

Related

• Deployment issues
• Troubleshooting overview