Persistent container creation failures in sfo region for evolution-api service
ivancsiqueira
FREEOP
a month ago
Hello, good morning!
I'm encountering this issue while trying to deploy my project.
Service ID: 401f8530-3b55-408e-b407-7e094f4cb2f0
Latest failed deployment ID: b8a1e2fb-3f02-493e-a526-52878e774c86
Problem: 4 identical CREATE_CONTAINER failures across Jul 8–10 in sfo region, all with generic "Failed to create deployment" error
Service config is valid; this is a platform-side provisioning issue requiring internal log inspection
1 Replies
Railway
BOT
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Hey! Change the source image of your service from atendai/evolution-api to evoapicloud/evolution-api.