The year is always wrong at the first api call so it returns no time slots available. I have explicitly have

now

directive on the prompt for what the current year is which from the other users here that experienced the same issue. Yet, still returns no available times. Inspecting it still uses 2023 as the year. But subsequent request on the same call corrects the api so its retrieving the correct time slots.

Hi binaryruel, For troubleshooting software issues that might be causing frequent crashes, consider the following steps: 1. **Update and Check System Requirements**: Ensure your software and its dependencies are updated to the latest versions to avoid compatibility issues. 2. **Review Recent Changes**: Identify any recent changes in the software environment that could have introduced the issue. 3. **Crash Logs**: Check the software’s crash logs for any patterns or error messages that may help identify the cause. 4. **Test with Different Configurations**: If possible, run the software with different configurations to see if the problem persists. 5. **Check for Deprecated Features**: Ensure that the software isn’t relying on any deprecated features. For example, the

codeSwitchingEnabled

property for Deepgram transcribers has been removed ([source](https://docs.vapi.ai/changelog/2025/6/24)). 6. **Consult Documentation**: Refer to official documentation for any known issues or updates that might resolve your problem. If you need detailed guidance on analyzing logs or specific configurations, let me know.

I have checked all of those already and still have the same output.

Current Date and Time Current date: {{ "now" | date: "%B %d, %Y", "America/New_York"}} Current time: {{ "now" | date: "%I:%M %p", "America/New_York"}} Day of week: {{ "now" | date: "%A", "America/New_York"}} Maybe this helps. Works for me for appts.

Yes, even though I have that, it always returns 2023 as the year.

{
  "calendarId": "my calendar id",
  "timeZone": "America/New_York",
  "startDate": 1694472000000,
  "endDate": 1695676800000
}

Hello, Thanks for reaching out to us. We are sorry for the inconvenience. Can you give more details about your concern? Your Org ID, email address and other details that will help us pinpoint your account and to look further into it? We will investigate further and we appreciate your kind understanding and patience.

All organizations under my account: rluna@binaryideas.com

Please also try adding something similar to this in the assistant prompt:

Do not use startTime and endTimes that are older than {{ "now" | date: "%s" | times: 1000 | tz: "America/Los_Angeles" }}

This worked. I've been finding solutions to this problem and this actually worked. Will test out to our other assistants.

Nice! Let us know if you run into any other issues