Hey there,

Cleared the bad sfo value and set hermes-agent to us-west2. Try a redeploy and it should go through.

Thanks for your patience,

Angelo

redeployed and the build still failed. same diagnostic message as well.

Sorry, the prior update didn't actually persist on our side. The stale sfo value was still in your service config when you redeployed, which is why you saw the same diagnostic. We've now written the region change directly (set to us-west2) and confirmed it stuck.

Please redeploy hermes-agent once more from the dashboard and the build should go through. If you spin up new services in this workspace and see the same sfo error again, let us know, your workspace preferredRegion may also need clearing.

just tried again, still failing unfortunately w same error. I accidentally tried to add a volume when there was already one attached during my setup, could that have something to do with it?

Likely so, looking into it again

Found the underlying issue. Your workspace's default region was sfo, which is why my fix kept getting rewritten back to sfo every time you redeployed. The volume add didn't cause it, it just triggered the rebuild that exposed the stale workspace default.

We've now updated your workspace default to us-west2 and reset the service config to match. Please redeploy hermes-agent one more time, the sfo value shouldn't come back this time. New services you create in this workspace will also default to us-west2 going forward.