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

you mention `pulumi refresh` twice, but was one of those mentions supposed to be `pulumi up`?

Not really, `pulumi up` seems to be working as intended reporting back the error message. But `pulumi refresh` should sync the states correctly, which doesn't appear to be happening.

I’m confused then because you say that refresh shows no changes, but then you also posted an error message. So is it failing on the error message or is it saying no changes? It can’t be both

Okay got it, the error message is coming from up, not refresh

The error message shows when I run `pulumi up` because pulumi thinks the droplet is still live when in fact it no longer exists. From my understanding, sometimes the state of pulumi vs what is actually provisioned can go out of sync for various reasons. `pulumi refresh` is supposed to fix such discrepancy but for some reason, it doesn't seem to be doing anything on digital ocean droplets.

When you run refresh what does it show on the right hand side for the droplet resource? I think you can also add a parameter to show a detailed diff

nothing appears on the right side of the droplet. (the plan column is empty) when I select details, this shows:
```details
  pulumi:pulumi:Stack: (same)```

You may also need to stack export &gt; state.json just to get an understanding of what’s in the stack state

Thanks <@U03CLBPHR0D>! I got it working by force deleting the state.

<https://www.pulumi.com/docs/cli/commands/pulumi_state_delete/>

Nice, you could also raise a bug for the digital ocean provider. It should have refreshed state properly