Please send your logs, ctrl/cmd+k -> logs

8d7c91f6-9d65-4dea-bdda-cdc0f4e83cc9

the same happende with this other one
2931f266-8803-4ef4-9a56-396d528abdbc

^

{
"severity": "info",
"timestamp": "2024-12-07T15:23:56.000000000Z",
"message": "Stopping Container",
"tags": {
"deploymentId": "4557c436-bd7f-4d81-88ea-e72f626f325f",
"deploymentInstanceId": "a50250f0-b12b-488c-ae5a-7d5cbd2b3c8a",
"environmentId": "9cb3b105-68b6-4f33-9dd3-88685bcb7ae4",
"pluginId": null,
"projectId": "8d7c91f6-9d65-4dea-bdda-cdc0f4e83cc9",
"serviceId": "d3c32a06-9d45-4015-9628-768798c95b6b",
"snapshotId": null
},
"attributes": {
"level": "info"
}
}

here is the JSON extracted from Dec 07 12:23:56

jumping in here as to not allow adam to go on a wild goose chase -

nacho, your deployments are removed when you push code.

new deployment happens -> old deployment removed.

thank you brody for the information!

but how come the container got just got started on nov. 9th?

obly?

shouldnt it be redeploy when i pushed code on the 7th? or am i missing some config?

you can also manually remove

from an admin prospective, i do not see any issues here.

adam, feel free to take this from here!

Fantastic thanks brody. nacho, if you have any questions let me know, but this is likely solved

It should redeploy every time you push code. Give it a try and if you see that behaviour then we’re good here

ok. i wil keep this in mind on the next deploy and see the behaviour. Thanks for the resposne

If you experience any other behaviour you don't expect, please open another help thread

!s