What happens when two iPhones edit the same Lesscue routine?

The practical answer

Lesscue’s optional Pro iCloud sync preserves pending local changes until the server confirms them and presents conflicting versions for review. It does not resolve every conflict by trusting whichever phone has the newest clock. Current protection remains local, and imported routine definitions require review before activation.

A setup to try

1. When sync reports a conflict, read both versions and decide which intended definition should survive. A newer-looking timestamp is not enough if a phone’s clock or edit context differs.
2. Keep the app’s pending-state distinction visible while offline. Do not reset local data merely to make a status badge disappear; that can remove useful context for the change you intended.
3. After changing the iCloud account, review the connection again. Pending records from one account should not be silently uploaded into another person’s private database.
4. For deletion, wait for the server-confirmed result. Reconnecting an older phone should not resurrect a record that was deliberately deleted in the synchronized dataset.

If two iPhones rename the same group differently, which name wins?

The sync design can preserve both conflicting versions for your choice rather than silently trusting device-clock order. Review the alternatives and choose the intended version. This is a definition conflict; the name decision should not rewrite app-selection tokens or end active protection on either phone.

What does Keep this iPhone mean on a sync-conflict screen?

It chooses the local version for the conflict being reviewed, rather than adopting the competing iCloud version. Read the affected fields before confirming. The choice concerns that synchronized record; it should not be interpreted as disabling all future sync or making local app selections transferable.

Why is a change still pending after I edited it successfully on the phone?

A local save and a server-confirmed sync are separate events. Offline connectivity, account availability, or another sync issue can leave the change queued. Keep using the local record as appropriate, but do not assume another iPhone has received it until the sync status confirms the transfer.

Will changing the iCloud account upload the old account’s pending records to the new one?

The intended behavior is to pause and require a fresh connection review, keeping account-specific pending state separate. A different iCloud account is a meaningful data boundary. Do not treat a successful system account switch as consent to move the previous account’s personal records into it.

Can a remote routine edit immediately change the apps blocked in my current session?

No. Active protection snapshots and current timers are excluded from sync. Remote definitions are reviewed for future use and should not weaken the local run underway. App-selection tokens are also local, so a remote name or time change is not a transfer of enforcement state.

If I delete a synced group, can an old offline phone recreate it later?

The synchronization design records deletion so an older live copy does not simply resurrect the same deleted identifier when it reconnects. Wait for the deletion to be confirmed and review any error state. An offline phone’s old display is not evidence that the server deletion failed.

Why does deleting cloud data ask for confirmation separately from pausing sync?

Pausing stops new transfers; deletion removes the existing synchronized dataset. Those are different outcomes, so the app should not hide a destructive action inside an ordinary Off switch. Choose pause if you want to retain the remote copy, and use explicit deletion when removal is intended.

What happens if iCloud storage is unavailable while I finish a focus session?

The local session record should remain saved while the optional transfer waits or reports its issue. A cloud failure is not a reason to invent a different local outcome. Check the pending queue and storage status later rather than interpreting the session as unsaved solely because sync could not finish.

Does turning sync back on automatically apply every remote routine as active?

No. Imported and remotely changed definitions require local review and are kept disabled for activation purposes. Confirm their times, ending methods, and locally selected groups before enabling them. Reconnection is not blanket consent for unseen schedules to start restricting the receiving iPhone.

Can I use iCloud sync as a guaranteed real-time remote-control panel for both phones?

No. The feature is selective record synchronization, subject to network and system delivery, not remote enforcement control. It excludes active sessions and permission state. Use the local app to inspect current protection, and treat last-sync information as evidence about records rather than a live view of another phone.