The build for that deployment exited at the BUILD_IMAGE step after 7 seconds with no application build output, which confirms the failure occurred before any of your code or configuration was evaluated. Your repository and build config are ruled out as causes.

Thanks for confirming that the repository and build configuration are not the cause.

Could you please confirm the remediation? The same commit has already failed three times: first at Snapshot Code and then at BUILD_IMAGE, both with “Failed to connect before the deadline”.

Can you retry the deployment on a healthy builder or clear any stuck builder/snapshot state for the service? If I need to trigger another manual redeploy myself, please confirm that this is now expected to work.

Service: leaseintel-api

Environment: production

Failed deployment ID: 7e41451c-aa68-4f95-84e0-00cafde5c6bd

The previous production deployment remains healthy.

Will dig into this shortly and update

Found the cause and it's a quick fix on your side. The service has a variable whose name is reports@leaseintel.co.uk, so an email address ended up in the name field. Our builder passes variable names into the build as secret references, and the @ makes that reference invalid. Every build dies a few seconds in because of it. The connection deadline message you saw is just the generic wrapper around that failure, which made it look like infrastructure, and our earlier automated reply sent you the wrong way. Sorry about that.

Delete that variable, or recreate it with a normal name like REPORTS_EMAIL and the address as the value, then redeploy. The same commit will build.

One footnote: your very first failure on Aug 18 at 21:34 was separate. We had a deployment incident that evening, your build actually completed and the deploy step failed on our side. That one was us.

thank you!