Check the saved plan
- Make sure your device has an internet connection and the app is open.
- Return to the agenda and reopen the event to check its latest details.
- Look for a loading, error, pending, or retry message. Do not assume a change saved while one is still showing.
- If an edit was rejected because the event changed, read the newest details before trying again.
Connected apps are designed to refresh when the family plan changes. Device-to-device delivery is still being validated during private testing, so confirm urgent changes directly with the other adult.
Plan for connection gaps
Depending on your test build, you may see a saved agenda, an event draft, or a pending request while offline. Saved details can be out of date. Reconnect and check the latest event before relying on a plan.
A pending change is not a confirmed change. If your build offers Retry or Discard, review the current event before retrying. Do not assume requests send automatically in the background. Push notifications and SMS are not a guaranteed way to receive event changes.
Report a problem with enough context
Never include passwords, login codes, or recovery links. A saved response and an alert are different things; the event’s current status is the place to check the plan.
- Say what you were trying to do and what you saw instead.
- Include your device model, app version, approximate time, and any error message.
- Say whether one device or both devices showed the problem.
- Remove names, addresses, invitation codes, and other private details from screenshots.