Hi Víctor, we've investigated and do not see any orphaned containers for the service you linked. Please point us to logs or anything else that would suggest any containers are running that shouldn't be, and we will investigate.

Hi Christian. Apologies for the confusion. We had the exact same situation a few months ago and assumed this was the problem.

We thought it was the phantom container thing because there were blockchain transactions being made (spending money thus the urgency) even if the worker service was not running. We believe this was caused by other thing but we are still unsure. Can you please confirm that there are no orphaned containers?

Thank you!

Thank you for the update, Víctor. I have escalated to our platform team to make sure there are no phantom containers running. I'll revert with an update as soon as possible.

We've confirmed there are no phantom containers running for the Worker service outside of the instances running in your production and testing environments that are visible on the Dashboard.