I can't deploy a new service connected to my GitHub repo. The service name is valiant-stillness, but it is not available from the below dropdown so I selected NA. Every attempt fails immediately with no build logs at all - just a generic "There was an error deploying from source" popup in the dashboard.

Checking the Network tab in my browser, the actual request behind that popup returns this:

{

"errors": [

    {

        "message": "Service Instance not found",

        "path": ["serviceInstanceDeploy"],

        "extensions": {"code": "INTERNAL_SERVER_ERROR"},

        "traceId": "7565828133669722192"

    }

],

"data": null

}

It's fully reproducible - I just tried again and got the same error with a new trace ID: 18331371889810353035

I deleted the service and created a brand new one from scratch, and got the exact same error again. I also can't rename the new service back to "eWeather" (its original name) - it says a service with that name already exists in the project, but nothing with that name shows up anywhere in the UI, in any environment.

Repo: ebs675/eWeather, branch main

Feels like there's a leftover service record on your end that's stuck and not showing up on my side. Would appreciate someone looking into trace IDs 7565828133669722192 and 18331371889810353035.