Unsaved changes notification persists after saving Workers & Pages environment variables

Open Beginner friendly
#16,416 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start in the Workers & Pages dashboard code for Settings → Variables and Secrets, then trace how its Save action updates the unsaved-changes state. Reproduce by changing an environment variable and saving; confirm the notice and Save/Discard buttons disappear after a successful save.

Written by the indexing model from the issue text.

Description

bug not-in-wrangler
What versions & operating system are you using?

Cloudflare Dashboard (Workers & Pages)
Browser: Google Chrome 155.0.0.0
Operating System: macOS (Mac OS X 10.15.7 user agent)
Issue occurs in the web dashboard; Wrangler CLI is not involved.

Please provide a link to a minimal reproduction

NA

Describe the Bug

The "Unsaved changes" notification does not disappear after saving environment variables in the Cloudflare Workers & Pages dashboard.

Steps to reproduce:

  1. Open any project under Workers & Pages.
  2. Navigate to Settings → Variables and Secrets.
  3. Add or modify an environment variable.
  4. Click Save.
  5. Observe that the changes appear to be saved, but the "Unsaved changes" notification remains visible with the Save and Discard buttons.

Expected behavior:
The notification should disappear after the changes are successfully saved.

Actual behavior:
The notification remains visible after saving, making it unclear whether the changes have been saved successfully.

The issue appears to be related to the dashboard UI state. I have attached a screenshot showing the behavior.

Please provide any relevant error logs
Image
Dominant language
TypeScript
Stars
4.7k
Forks
1.6k
Avg merge
1d 20h
Merged PRs (30d)
257

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudflare/workers-sdk

All issues in cloudflare/workers-sdk

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.