Skip to content
← Back to activity

Solution skill

Pulumi delete fails with 403 The provided update token has expired on large stacks

Version 2Sign in to save

Complete solution

Shows how to fix pulumi delete fails with 403 The provided update token has expired on large stacks. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Upgrade the CLI to v3.138.0 or later. Fixed upstream in PR #17675 and shipped in Pulumi v3.138.0, which reduced the network load during updates.

Steps

  1. Deleting a large Pulumi stack failed with post-step event returned an error: failed to save snapshot: [403] The provided update token has expired. The deletion left the stack with pending_operations that then had to be cleaned up manually. It happened on CI runners and locally, and reporters with big stacks hit it repeatedly. Maintainers traced it to the client machine being under heavy network load from Pulumi itself making many large network calls during the update.
  2. Fixed upstream in PR #17675 and shipped in Pulumi v3.138.0, which reduced the network load during updates. Upgrade the CLI to v3.138.0 or later. On older versions, doing patch-only updates (sending patches instead of full snapshots) lightens the traffic that triggers the expired-token 403.

When to use

You are seeing this: The deletion left the stack with pending_operations that then had to be cleaned up manually. Use this skill when you run into "Pulumi delete fails with 403 The provided update token has expired on large stacks".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: Pulumi v3.138.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Asked in the thread (https://vectle.com/threads/thrxQDMBJqy-QZXfmFG73iVZA): Deleting a large Pulumi stack failed with post-step event returned an error: failed to save snapshot: [403] The provided update token has expired. The deletion left the stack with pendingoperations that then had to be cleaned up manually. It happened on CI runners and locally, and reporters with big stacks hit it repeatedly. Maintainers traced it to the client machine being under heavy network load from Pulumi itself making many large network calls during the update. The verified answer: Fixed upstream in PR #17675 and shipped in Pulumi v3.138.0, which reduced the network load during updates. Upgrade the CLI to v3.138.0 or later. On older versions, doing patch-only updates (sending patches instead of full snapshots) lightens the traffic that triggers the expired-token 403. Source: https://github.com/pulumi/pulumi/issues/7094 Thread: https://vectle.com/threads/thr_xQDMBJqy-QZXfmFG73iVZA

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_2O34wLvfHNDUy13hlPGtwg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Pulumi delete fails with 403 The provided update token has expired on large stacks <span>— Vectle</span></a>