Why editing an app group does not rewrite a running session

The practical answer

A saved group is a reusable definition; a running Lesscue session uses the selection and ending policy captured when it started. Editing the saved group changes future starts rather than silently rewriting active protection. Changes to Always Allowed that weaken current protection are different and must pass the strongest affected ending policy.

A setup to try

1. Before editing, identify whether your goal concerns a future session or the current run. The two actions have different consequences and should not share an ambiguous save button.
2. For future changes, edit the saved group or routine and keep the active snapshot intact. Read any explanation that the current occurrence continues until its original end.
3. For an essential exception needed now, review the impact on all affected active protections. Confirm, the optional pause, or Locked policy may apply depending on the strongest affected run.
4. After the current session ends, test the updated group with a short new session. A saved edit is not evidence that the current timer already adopted the new selection.

If I remove Instagram from a saved group, does the running session unblock it?

Not through a future-definition edit. The active session keeps the selection snapshot captured when it began, while the edited group applies to future starts. If you need a current change, use the appropriate release or exception flow and read its effect on active protection.

Why does renaming a routine not end the occurrence already running?

A name edit can update the future definition without discarding the active occurrence and its original endpoint. That separation lets you organize schedules without accidentally releasing protection. Check the active state independently rather than assuming every routine edit restarts or stops the current run.

Can I pause tomorrow’s routine while today’s occurrence continues?

The product separates future starts from the currently active occurrence. A future-only pause can preserve today’s captured protection and original ending callback. Read the edit scope before saving so a schedule-management action is not mistaken for an immediate release of the present window.

If I delete a future routine definition, will its active block disappear instantly?

A future-only deletion preserves the current occurrence until its original end. Ending that occurrence is a separate weakening action governed by its mode. The interface should state which scope you are changing rather than letting the word Delete imply an undisclosed immediate unblock.

Why does adding Always Allowed ask for confirmation during focus?

An exception can relax protection that is already active, so it is not merely an organizational edit. Lesscue checks the strongest affected mode and reviews the impact before applying it. Prepare essential apps before starting when possible, especially if you intend to use Locked.

Does removing an app from Always Allowed require the same early-ending wait?

No. Removing only an Always Allowed exception does not require the early-ending wait; it strengthens protection. The app may then fall under an existing block. If the same edit also adds another exception, that addition is evaluated separately and can require confirmation or be refused during Locked protection.

What if the same app is affected by two active routines with different modes?

The relevant weakening decision uses the strongest affected active policy. A Confirm routine should not provide an indirect way to relax an overlapping Locked one. Read the impact summary and original endpoints before assuming that changing one definition removes every restriction on the app.

Can a group edit arriving from iCloud weaken the session already running here?

No. The sync contract keeps active protection outside the transfer payload and preserves current snapshots. Remote names or future definitions are not release commands. Review imported changes for later use while treating the current local run as a separate protected state.

Do I have to recreate a whole group every time my work tools change?

No. Reusable saved groups exist so you can adjust future selections without rebuilding every routine from scratch. Make the change when you can review the picker clearly, then verify a new session. The distinction is about timing of application, not a requirement to duplicate groups unnecessarily.

How can I tell whether an edit applies now or only to future sessions?

Look for the scope explanation and the list of affected active protection before confirming. A future-only save should preserve the current snapshot; a weakening action requires the appropriate gate. If the screen does not make that difference clear, do not infer it from the button’s color or position.