#Deploy Error: Unable to acquire machine

1 messages · Page 1 of 1 (latest)

versed valley
#

Hi Team, we were just trying to deploy to Trigger and suddenly we are experimenting with an error:

◒  Building version 20250508.2...
◐  Building version 20250508.2: #1 [depot] launching amd64 machine...
◓  Building version 20250508.2: #1 ERROR: unavailable: Unable to acquire machine, please retry...
◑  Building version 20250508.2: #2 [depot] launching amd64 machine...

Will be posting the logs here.

torn bluffBOT
#

Hi @versed valley. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

I can see you're experiencing an error during deployment to Trigger.dev. The error message "Unable to acquire machine, please retry" suggests there's an issue with the build process when trying to allocate resources for your deployment.

Based on the knowledge sources, this appears to be a temporary infrastructure issue rather than a problem with your code or configuration. The system is trying to launch an AMD64 machine for building your deployment but is unable to acquire the necessary resources.

Troubleshooting Steps

Here are some steps you can try:

  1. Retry the deployment - Sometimes simply retrying the deployment can resolve temporary resource allocation issues.

  2. Use debug logging - Run the deploy command with additional debug information to get more insights:

    npx trigger.dev@latest deploy --log-level debug

    This will provide more detailed information about what's happening during the build process, as mentioned in the Troubleshooting documentation.

  3. Try a dry run - You can use the --dry-run flag to test the build process without actually deploying:

    npx trigger.dev@latest deploy --dry-run

    This will build your project locally and show you where the built files are located, allowing you to inspect them for any issues as suggested in the CLI deploy command documentation.

  4. Check for version mismatches - Ensure all your Trigger.dev packages are on the same version. You can run the update command to synchronize them:

    npx trigger.dev@latest update

    As mentioned in the Upgrading Packages documentation, version mismatches can cause deployment issues.

#

If the problem persists, it's recommended to join the Trigger.dev Discord and create a help forum post with your deployment logs (with sensitive information removed). The error you're seeing appears to be related to the build infrastructure rather than your code, so the Trigger.dev team would be best positioned to help resolve it.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@versed valley Kapa.ai is still learning and improving, please let me know how I did by reacting below.

versed valley
#

Seems it's an issue when deploying, because it works when doing the --dry-run command

iron hull
#

Yeah, I believe that's a Depot service issue

versed valley
#

Stuck at ◐ Building version 20250508.4: #1 [depot] launching amd64 machine...

#

😭 ohhhh

iron hull
#

@unborn hearth FYI

versed valley
#

Just when we released a breaking change to our backend but the trigger.dev hasn't been updated lol

unborn hearth
#

Yeah we need to figure out how to mirror their status for their Docker service. Annoyingly that’s not possible with BetterStack

#

I’ve been speaking to them and a fix is coming soon. It is still working but not as much as normal

#

Keep trying to deploy

versed valley
#

Hmm, isn't there is a way to ingest depot's RSS on betterstack?

unborn hearth
versed valley
#

Ahh

unborn hearth
#

The issue is Depot do multiple things and GitHub Actions have a lot more problems, and we don’t use that

#

So we’d end up with a lot of false positives

#

So for now we do the above

versed valley
#

Gotcha! Does that regularly happens with Depot? Well, in the meantime will just keep trying the deploy.

unborn hearth
#

All GithubQction runners have the same problem with GH themselves…

They’re rarely down for the docker builds which we use

pliant bluff
#

I'm also facing the same issue 😭

#

do we just need to keep deploying?

#

i also getting this error, is this related with this issue too? @unborn hearth sorry for tagging

image.png
iron hull
#

What's the error in that log?

versed valley
#

Maybe be something like:

#1 [depot] launching amd64 machine
#1 ERROR: unavailable: Unable to acquire machine, please retry
#2 [depot] launching amd64 machine
#2 ERROR: unavailable: Unable to acquire machine, please retry
------
> [depot] launching amd64 machine:
------
------
> [depot] launching amd64 machine:
------
Error: unavailable: Unable to acquire machine, please retry
pliant bluff
#

yep its same

pliant bluff
versed valley
#

Seems resolved in my end, was able to deploy

#

FYI

pliant bluff
#

yep, mee too