6 months ago
Hello team,
I'm encountering a critical platform bug that prevents me from adding any second service to my project.
The Problem:
I can always deploy the first service from my GitHub repo without any issues. However, any attempt to add a second service fails immediately with the error: Failed to deploy! Service Instance not found.
Key Information:
The most critical detail is that this also happens when I try to create an Empty Service. The operation fails with the exact same Service Instance not found error. This confirms the issue is not related to my Git repository, monorepo setup, or user error.
Troubleshooting Steps Taken:
I have deleted and recreated the entire project multiple times, and the bug is consistent.
The first service always deploys, the second one always fails.
The failure occurs even with the most basic "Create Empty Service" action.
This strongly suggests a project-level provisioning bug on the platform where the project gets into a corrupted state. Could you please investigate?
My Project ID is: 71618e7d-2aa5-406d-9f51-05051018df92
Thank you for your help!
2 Replies
6 months ago
Same here. I have a monorepo and I'm attempting a third service instance of the same repo but with a different toml. It won't even start deploying.
Now I can create an empty service but when trying deploying from github, the bug reappears (first service deployed, second fails)
