@broad-dog-22463,

pulumi up --refresh

should discover that cloud resource was deleted, right? It was deleted due to 'deleteBeforeCreate' on a previous run, then creation failed, so now I am adding '--refresh' in a hope that pulumi will figure out that resource is not there anymore, but it still tries to update 😕

Try Pulumi refresh directly and see if it notices it

simple retry on CI succeeded , it seems that response was cached by a our proxy or GCP API is eventually consistent

Ah ok! Good to hear