Catch feature flag drift between ConfigCat environments
Every night, WebRun opens ConfigCat, compares flag targeting rules and rollout percentages between staging and production, logs any mismatch to Airtable with both values, and posts a Notion summary so a flag that quietly drifted out of parity gets caught before it causes confusion.
- No credit card
- Under $0.01 per run
- Cancel anytime
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.configcat.com/auth/loginin a real browser with your saved login - no setup, no API keys. -
1
ConfigCat - compare environment settings
configcat.com
WebRun opens ConfigCat to compare environment settings. - Open ConfigCat and review flag settings in both staging and production
- Compare targeting rules and rollout percentage for each flag between the two environments
- Note any flag where the two environments do not match
Done when Every flag is compared between staging and production with any mismatch noted.
-
2
Airtable - log the mismatches
airtable.com How to Automate Airtable
WebRun opens Airtable to log the mismatches. - Open the ConfigCat Parity base
- Add a row for each mismatched flag with its staging and production values
- Mark any mismatch already logged the prior night as still open
Done when The Airtable base lists every flag currently out of parity between environments.
-
3
Notion - post the drift summary
notion.so How to Automate Notion
WebRun opens Notion to post the drift summary. - Open the engineering Notion page
- Post tonight's drift summary naming each mismatched flag and its two values
- Ask the flag owner to confirm whether the difference is intentional
Done when Engineering has tonight's environment parity summary in Notion.
How do I catch ConfigCat flags that drift out of sync between environments?
WebRun compares ConfigCat flag targeting rules and rollout percentages between staging and production every night, logging any mismatch to Airtable with both values. It then posts a Notion summary for the flag owner to confirm, so a flag that quietly drifted out of parity between environments gets caught before it causes a confusing bug.
- Flag drift between environments is caught the same night it happens
- Every mismatch gets a named owner to confirm instead of staying silent
- Production surprises from a forgotten staging-only setting drop sharply
Built for Engineering teams · platform engineers · release managers · QA teams
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will WebRun fix the mismatch by changing a flag itself?
No. It only detects and reports the difference. Changing a flag's settings in either environment stays a decision for the flag owner.
What if the difference between environments is intentional?
It still gets listed, since the report is about visibility, not judgment. The flag owner can confirm it is fine and it will keep showing until acknowledged or the values match.
Does it compare every flag or only some?
Every flag that exists in both the staging and production environments you connect it to.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.