---
title: "Verify scheduling rejects or resolves a missing local time"
description: "Test a sandbox scheduler at a daylight-saving spring transition, checking its documented treatment of a local time that does not exist."
canonical_url: "https://vostride.com/agent-library/scheduling/spring-forward-missing-time.md"
md_url: "https://vostride.com/agent-library/scheduling/spring-forward-missing-time.md"
content_kind: "recipe"
topic: "scheduling"
---

# Verify scheduling rejects or resolves a missing local time

Test a sandbox scheduler at a daylight-saving spring transition, checking its documented treatment of a local time that does not exist.

## Risk

A local-time picker can accept a nonexistent hour and silently schedule a different instant. This recipe uses a prepared timezone transition and an explicit product policy instead of assuming that every scheduler should reject the same input.

## Fixtures

- An owned sandbox scheduler with a disposable calendar and a supported timezone whose spring transition is recorded in the fixture.
- A product requirement defining whether a nonexistent local time is rejected or explicitly moved to the next valid instant.
- An external clock and timezone fixture plus a read-only event oracle exposing local time, zone, and canonical instant; no device clock manipulation is assumed.

## Steps

1. Open a new event on the prepared transition date and verify the calendar displays the intended timezone.
2. Choose the fixture nonexistent local time and verify the documented validation or explicit adjustment explanation appears before commitment.
3. Apply the product-supported resolution, save, and verify the confirmation clearly shows the final valid local time and timezone.
4. Reopen the event and inspect the independent oracle; verify the stored instant maps to the confirmed local time and that only one event exists.

## Expected results

- The product never silently represents the missing time as a valid unqualified appointment.
- The final canonical instant matches the explicitly confirmed resolution.
- The saved calendar contains one event in the intended timezone.

## False-pass traps

- Testing an ordinary date cannot expose the missing-hour path.
- A formatted time without its timezone can conceal an unintended conversion or adjustment.

## Cleanup

- Delete the sandbox event and restore the external clock and timezone baseline.

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