If a remote workspace does not connect, see the workspace Troubleshooting.
The pipeline is red
In GitLab under CI/CD → Pipelines, open the job marked red; the error message is usually at the end of its log and can often be reproduced locally with ap run-local. Fix the cause and push again without changing .gitlab-ci.yml; if the log does not help, send the pipeline link to support, and What are pipelines? explains the structure.
The page is not reachable
Check whether the last pipeline passed, whether a server is assigned to the project, and whether the manual production job was started. If the dev address works but your domain does not, the check mark under Domains in the Status column is usually missing; then compare the DNS records with those at your domain provider, see Configure DNS.
The agent reports that you are not signed in
Type ap login, check your account with ap whoami, and repeat the request. If the MCP server application-platform is missing, repeat the installation from Work with an AI agent and reload the editor; if ap is not found, the ap CLI from the downloads page is missing.
The application does not start
If ap run-local aborts because a port is in use, stop the old process or Docker container; if a runtime is missing although installed, you are not in the repository folder with the matching .tool-versions. ap doctor and the Developer setup of the setup app show missing tools; further points are in Open and run your project.
Support and feedback
The support page, in the platform under More → Help, offers a form and German and English WhatsApp groups; we usually reply within one business day. State organization, project, what you expected, and what happened instead, ideally with the error message or pipeline link, but without passwords or credentials.
Wishes and notes on unclear passages in the documentation go to the feedback page.