---
title: "Verify rescheduling replaces the attendee notification"
description: "Test a sandbox meeting reschedule, checking that attendees see the new time and the notification payload points to the updated event revision."
canonical_url: "https://vostride.com/agent-library/scheduling/reschedule-updates-attendee-notice.md"
md_url: "https://vostride.com/agent-library/scheduling/reschedule-updates-attendee-notice.md"
content_kind: "recipe"
topic: "scheduling"
---

# Verify rescheduling replaces the attendee notification

Test a sandbox meeting reschedule, checking that attendees see the new time and the notification payload points to the updated event revision.

## Risk

A calendar can update immediately while an attendee notification still carries the old schedule. Inspect the independently captured sandbox message and event revision together instead of relying on organizer-side success.

## Fixtures

- An owned sandbox meeting with one test organizer and one disposable attendee, plus a baseline event revision and initial notification.
- A sandbox notification sink and external dispatch fixture that records when reschedule messages are processed.
- A read-only event and delivery oracle exposing revision identifiers, start times, and recipient identifiers without sending to real people.

## Steps

1. As organizer, open the event, change its start and duration, and verify the review shows the intended new schedule.
2. Save and verify the organizer detail displays the new time and duration after reopening.
3. Run the prepared external dispatch checkpoint and verify the sandbox sink receives one update for the test attendee.
4. Inspect the update payload and independent event oracle, verifying the same event identity and new revision; open the attendee view and verify the updated time rather than the original schedule.

## Expected results

- Organizer and attendee views resolve to the same updated event revision.
- The update notice contains the new schedule and intended sandbox recipient.
- No duplicate active event or stale replacement invitation is created.

## False-pass traps

- A delivered-message count alone does not prove its payload contains the new time.
- The organizer success page can pass while the attendee remains attached to an obsolete event copy.

## Cleanup

- Delete the sandbox meeting and clear its captured notification fixture.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa hooks](/docs/agent-qa/guides/hooks.md)
- [agent-qa test](/docs/agent-qa/configuration/test.md)

- [Scheduling and calendar QA recipes](/agent-library/scheduling.md)
- [Software factory QA library](/agent-library.md)