---
title: "Verify scheduling disambiguates a repeated local time"
description: "Check a sandbox appointment in a daylight-saving repeated hour, verifying the selected occurrence, stored offset, and reminder instant agree."
canonical_url: "https://vostride.com/agent-library/scheduling/fall-back-repeated-time.md"
md_url: "https://vostride.com/agent-library/scheduling/fall-back-repeated-time.md"
content_kind: "recipe"
topic: "scheduling"
---

# Verify scheduling disambiguates a repeated local time

Check a sandbox appointment in a daylight-saving repeated hour, verifying the selected occurrence, stored offset, and reminder instant agree.

## Risk

Two different instants can share the same local clock label. A passing check must identify which occurrence was selected, using an independently prepared offset expectation and the product documented ambiguity policy.

## Fixtures

- An owned sandbox calendar and a test user with a timezone that has a prepared fall transition date.
- A fixture defining the two valid offsets for the repeated local time and the product method for choosing or documenting its default occurrence.
- An external clock fixture and read-only event/reminder oracle; reminder delivery is routed to a sandbox sink.

## Steps

1. Open the prepared date, select the repeated local time, and verify the interface exposes the occurrence choice or documented default explanation.
2. Choose the required fixture occurrence and verify the confirmation displays enough timezone or offset information to identify it.
3. Save and reopen the event, then verify its duration and displayed start still correspond to that occurrence.
4. Inspect the independent event and reminder oracle and verify the stored instant and reminder due instant match the selected offset, with one event and one reminder.

## Expected results

- The selected occurrence has the expected canonical instant rather than its one-hour neighbor.
- The reopened event preserves the selected ambiguity resolution.
- The reminder is derived from that same instant and configured lead time.

## False-pass traps

- Comparing only the local hour cannot distinguish the two occurrences.
- A reminder generated from a different offset may appear correctly dated while firing an hour early.

## Cleanup

- Remove the sandbox event and pending reminder, then reset external time fixtures.

## 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)