Resume an open calendar after being idle

User intention

After lunch, continue checking appointments in the calendar I left open.

The intention is included in the agent’s input prompt alongside environment details and task instructions.

What breaks, and what should happen

Play Both
BeforeThe defect at the parent commit
0:00.00 / 0:00.00Frame 0 · Leave the calendar page open and return after the wait.

After the wait, the calendar still shows the original day view. Trying Week leaves the calendar area blank and changes its tab label to Unknown.

AfterThe same script once the merged fix is applied
0:00.00 / 0:00.00Frame 0 · Leave the calendar page open and return after the wait.

After the wait, the page shows a sign-in form. Submitting credentials and closing the registration dialog restores the calendar day view.

How is it judged?

01 · Given
Restore the data and starting state.
An administrator is signed in with Calendar and Message Center loaded in a single browser tab and normal background reminder polling active.

02 · When
Perform the interaction.
Leave the calendar open without interacting until the session expires from inactivity, allowing background reminders to poll normally. Return to the calendar and try switching to the week view if the option is still available.

03 · Judge
Rationale: Returning to the calendar left open before lunch is a natural way to continue checking appointments. The calendar view and background reminders depend on an authenticated session. After it expires, the old schedule may remain visible even though subsequent calendar requests require the user to sign in again. Clear authentication feedback helps the user distinguish an expired session from an empty schedule and provides a way to resume checking appointments.
Require
When the open calendar detects that the session is no longer valid, it must show the sign-in page or explain that authentication is required and provide a working sign-in option. It must not leave an unexplained blank or Unknown area. Protected calendar operations may resume only after the user authenticates again.
Allowed
  • The application may redirect directly to the sign-in page.
  • The application may clearly explain that the session has ended and provide a working sign-in button or link.
  • The application may detect the expired session through a background request or the next protected operation; it does not have to redirect at the exact moment the idle timeout is reached.

Who repaired it