This message was deleted.

Hi, try running

pulumi refresh

to update the Pulumi state with the latest changes. Then you can continue either deploying with

pulumi up

or destroying with

pulumi destroy

I’m still getting the same error

I see that there are 2 `awsecsTaskDefinition`s that may be interfering with each other. Maybe you can double check them. If that does not work, you can try fixing by configuring dependencies for the failing asset - the root level

aws:ecs:TaskDefinition

.