No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

We are getting `Target 'urn:XXX' could not be found in the stack` error when trying to apply resource. However, we can see the resource with the urn both in the state and AWS console. What could that mean and what could be the fix?

it also shows resource to be deleted in the plan

```Previewing update (single-region-test):
     Type                              Name                                    Plan       Info
     pulumi:pulumi:Stack               single-region-stack-single-region-test             3 errors
 -   ├─ aws:ec2:RouteTableAssociation  eu-west-1c-public                       delete     
 -   ├─ aws:ec2:Route                  eu-west-1c-public                       delete     
 -   └─ aws:ec2:Subnet                 eu-west-1c-public                       delete     
 
Diagnostics:
  pulumi:pulumi:Stack (single-region-stack-single-region-test):
    error: Target 'urn:pulumi:single-region-test::single-region-stack::dycloud:index:Ec2Vpc$dycloud:index:Subnet$aws:ec2/routeTableAssociation:RouteTableAssociation' could not be found in the stack.
    error: Target 'urn:pulumi:single-region-test::single-region-stack::dycloud:index:Ec2Vpc$dycloud:index:Subnet$aws:ec2/subnet:Subnet::eu-west-1c-public' could not be found in the stack.
    error: Target 'urn:pulumi:single-region-test::single-region-stack::dycloud:index:Ec2Vpc$dycloud:index:Subnet$aws:ec2/route:Route::eu-west-1c-public' could not be found in the stack.```

I've honestly never seen this error, very surprised the stack is in this state:

• can you share the code you're using to define your program
• can you shack the output of `pulumi stack export` (in a github gist if it's long)

it looks like this is caused if you run pulumi up targeting a custom resource and it has other resources nested under it

we can't publish state, sorry :slightly_smiling_face: