Docs
Limits & FAQ
Last updated:
Use this guide to check the next practical step when a deployment, connection or resource action does not behave as expected.
On this page
Where do I find my limits?
Review your workspace’s usage and resource settings. Capacity, account permissions and limits can prevent resource creation or deployment. Use the actual error message to identify which constraint applies; do not assume every failure requires a plan upgrade.
Why did my deployment fail?
- Build failure: inspect dependency errors, build configuration and required variables.
- Startup or health failure: verify the production command, configured port and health-check response.
- Infrastructure failure: inspect target availability and the connected server’s agent status.
Can I roll back?
Use the deployment actions offered for an eligible previous deployment. Availability depends on its retained image and deployment type. A rollback is not a database restore; validate schema compatibility. Do not assume a failed deployment always leaves the previous version serving.
Can I deploy a Docker image or public URL?
These guides cover connected GitHub repositories and build methods available in the product. A repository Dockerfile does not imply that direct public GitHub URL or prebuilt Docker/OCI image deployment is available. Use only a source option offered by your workspace.
What should I send to support?
Include the affected workspace/app identifier, deployment identifier, timestamp, action and relevant error excerpt. Remove credentials, tokens and connection strings. Use the support contact in the site footer; no response-time guarantee is implied.
Ready to deploy your application?
Start for free