# agent scheduled a 30-minute screen but the calendar defaulted to 60 - the event-length override never applied

## TL;DR

The agent passed a 30-minute duration, the calendar API ignored the override, and the event booked at the 60-minute default. Verify the created event's duration in the API response, and set the default event length correctly as a backstop. Trust the response, not the request.

```text
agent scheduled 30-minute screen but calendar defaulted to 60 - event-length override never applied
```

## Steps

1. Confirm the override failure: compare the requested duration against the created event's actual length.
   Expected: The event is 60 minutes despite the 30-minute request.

2. Check how the duration was passed: some calendar APIs take duration in the event body, others only respect the calendar's default.
   Expected: The override went to a field the API ignores.

3. Fix the call to use the API's real duration mechanism, and set the calendar's default event length to 30 minutes as a backstop.
   Expected: New events book at 30 minutes.

4. Verify in the create response: assert the returned event's duration matches the request before confirming to the candidate.
   Expected: Mismatches fail loudly.

5. Fix the wrongly booked events: shorten them and notify the participants.
   Expected: The calendar reflects the intended lengths.

## When to use

- events book longer than requested
- the agent passes duration to the calendar API
- screens default to 60 minutes

## When not to use

- the duration is correct in the response (check the display instead)
- the 60 minutes is the calendar's default and also correct (then it is not a bug)
- the API documents that it ignores duration (use the supported mechanism)

## Tool compatibility

- Google Calendar / Outlook event APIs
- scheduling agents

## Variant phrasings

- "calendar event length override ignored"
- "30 minute screen booked as 60"
- "event defaulted to 60 minutes"

## Why it happens

Calendar APIs have defaults, and duration overrides live in specific fields that vary by API. An agent that passes duration in the wrong field gets the default silently: the API does not error, it just books an hour. The request looked right; the response told the truth nobody read.

## Edge cases

- recurring events can have per-instance overrides; check the instance, not the series
- the default event length is a calendar setting worth setting deliberately
- candidate-facing confirmations should state the duration so errors surface fast

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_8c3A91W7bVoEpMLMvregeA
