Flag lifecycle

Every production flag needs an owner and a removal plan. Toggld supports permanent deletion, but it has no archive state and no automatic expiry. Use these procedures to keep your flags under control.

Introduce a flagCopy Anchor Link

1. Assign an owner before the first production use.
2. Record the purpose, the responsible team, and a review date in the flag Description. Review dates are a team procedure. Toggld does not act on them.
3. Choose a safe fallback value in your code and an explicit off variant.
4. Create the flag and test it in Development before you turn it on in Production.
5. Test the contexts that your rules target, and the case where no rule matches.

Each environment stores its own values and rules. Your edits stay in a draft until Save environment succeeds. Test a user shows what a context gets from the saved rules. It does not prove that your application receives updates. Confirm that your application receives the expected value before you increase a rollout.

Change production behaviorCopy Anchor Link

1. Select the Production environment tab before you edit. Check for the Live badge on the tab.
2. Review the variants, the default variant, the off variant, and the rule order.
3. For a percentage rollout, give at least one variant a positive weight.
4. Save the environment.
5. Wait for the success message before you treat the change as live.
6. Test the result through your application.
7. Check the recorded evaluations in the flag's Evaluations panel.

SDKs that use local evaluation work from a synchronized copy of the definitions. Polling, caches, and network access affect when a change arrives. Fast evaluation does not mean immediate delivery of updates. Keep your fallback values safe during an incident. See how fast changes arrive.

Restore a bad changeCopy Anchor Link

Toggld has no one-click restore during the beta. Use the audit log to find the previous configuration and apply it again.

1. Open Audit log in the affected workspace.
2. Filter by the flag key.
3. Open an earlier saved change that contains the configuration you want, with View saved change.
4. Note the environment, variants, default variant, off variant, and targeting rules from that event.
5. Open the flag and select that environment.
6. Apply the earlier values to the draft.
7. Review the draft.
8. Save the environment.
9. Test the result in your application.

The audit log shows the latest 100 matching events. Filter by resource to find older events. If you cannot find the history that you need, contact support before you change values that you do not understand. During recovery, use a known safe configuration or rely on your fallback values. See Audit log.

Retire a flagCopy Anchor Link

1. Agree on the permanent behavior with the flag owner.
2. Remove the flag lookup from your code.
3. Deploy that change to every application instance that uses the key.
4. Make sure that old instances and scheduled jobs no longer read the flag.
5. Record the retirement decision in the description.
6. After all readers are gone, open the flag's Delete section and delete the flag.

Deletion removes the flag from every environment, and you cannot undo it in the product. Any code that still reads the key receives its fallback value with the error code FLAG_NOT_FOUND.

Keep the key and its permanent value in your team's change record.

Remove an unused workspaceCopy Anchor Link

1. Delete the workspace's flags and segments.
2. If other members remain, transfer ownership before you leave the workspace.
3. If you are the only member, open Settings → General.
4. Read the deletion consequences.
5. Type the workspace URL name to confirm.
6. Delete the empty workspace.
7. To delete your account as well, open Account and security.

Removing a workspace deletes its environments, credentials, invitations, and history.

Contact support@toggld.io for beta access problems or incidents. Never send credentials, session cookies, or private targeting data.