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

:wave: Hi everyone!

I try to make a database in gcp, but I always have a timeout and then I always have a stale state. I can't understand what I'm supposed to do, Am I missing something?

```error: post-step event returned an error: failed to save snapshot: renewing lease: [403] The provided update token has expired.```
all the <https://www.pulumi.com/docs/support/troubleshooting/#interrupted-update-recovery|troubleshooting>  tells me to do is delete the resource and presumably try again.... But the database call takes too long and the token expires?

Any advice at all? 

Is there a way to manage this situation? It seems popular

<@U03K3G5S4E6> how long is the database taking to create? what state store are you using?

Database takes like more than 10 minutes. Just default for gcp

is this a large stack with lots of resources?

I'm just making a database with a private ip

The database creation works but pulumis token is always expired at that point

so you're storing in the Pulumi service backend, using a standard `pulumi login` token?

Nothing is non standard just going for default functionality

But that database is always stuck in pending

could you file an issue with your code and your org name in pulumi/pulumi, it sounds like a bug

Yeah I'll do an issue thanks. 

Found this in the meantime <https://github.com/pulumi/pulumi/issues/7094|https://github.com/pulumi/pulumi/issues/7094>

<@UCWG26BH7> <https://github.com/pulumi/pulumi/issues/7094#issuecomment-1154656563>