F

VAPI•7mo ago

forward-apricot

Critical Issue: Inconsistent Timezone Handling in google_calendar_check_availability_tool

Dear VAPI Support Team,

I am writing to report an ongoing and critical issue affecting the google_calendar_check_availability_tool, which is currently producing inconsistent timezone handling and mismatched time intervals between the request (tool_call) and the response (tool_call_result). This makes it unreliable for scheduling availability slots.

⸻

Example 1 – Call ID: ecbd4161-9e1f-49b0-8e90-73ee2d38eea5

Request:

{
"startDateTime": "2025-06-03T17:30:00+02:00",
"endDateTime": "2025-06-03T18:00:00+02:00",
"timeZone": "Europe/Madrid"
}

Result:

{
"busy": [],
"free": [
{
"start": "2025-06-03T15:30:00.000Z",
"end": "2025-06-03T16:00:00.000Z"
}
]
}

Problems:
• Response is in UTC (Z), not in the requested +02:00.
• The returned interval (15:30–16:00 UTC) does not correspond to the requested range (17:30–18:00 CEST).

⸻

Example 2 – Call ID: d9ef775a-b435-4c54-9d13-34b2cb1bed6d

Request:

{
"startDateTime": "2025-06-03T18:00:00+02:00",
"endDateTime": "2025-06-03T18:30:00+02:00",
"timeZone": "Europe/Madrid"
}

Result:

{
"busy": [],
"free": [
{
"start": "2025-06-03T16:00:00.000Z",
"end": "2025-06-03T16:30:00.000Z"
}
]
}

Problems:
• Times are again returned in UTC instead of +02:00.
• The interval does not match the time range queried.