percy is wrong the project is cc6da1e6-256c-47fc-bf86-2d464d8eb369

and 66f1914a-8072-47f5-9bc0-eee78a27a6d3 is the service

the one that was deploying in the top screenshot failed and now it shows this:

is the database still on metal?

its on metal right now yeah

i used mongodump and mongorestore to move the data to a metal volume last week or so, and it was working for a while

oh interesting, alright I'll flag the team into this thread

!t

hello @Erisa do you have a way to reproduce this, or steps that lead up to this issue?

Not really, besides what i mentioned in the first message, but it does look like it's suddenly started deploying again?

I dont think I triggered that deploy, dont know where it came from

i didnt do it, maybe my team mate did

where you trying to re-size it?

Never tried to resize it - I was fiddling with the arguments in the start command, trying (and failing) to lower mongos cache size

The deployment that crashed is because I botched an arg, and then it started failing to deploy after I reverted back to the default args

is it reproducible?

I don't know sorry, I don't have the time to spin up another and try doing all the same steps to check, especially since it apparently works now

Was mostly just confused that there was no error presented when it failed, so it wasn't clear what I could try to help fix it

I'm just going to not touch this service anymore and hope it stays working now that its working

okay, thank you anyway!

thanks for the help!

no problem!

!s