thecurtis
06/04/2025, 8:26 AMVapi Support Bot
06/04/2025, 8:27 AMthecurtis
06/04/2025, 8:28 AMKings_big💫
06/04/2025, 8:31 AMthecurtis
06/04/2025, 8:32 AMKings_big💫
06/04/2025, 8:42 AMthecurtis
06/04/2025, 8:45 AMthecurtis
06/04/2025, 8:46 AMKings_big💫
06/04/2025, 8:46 AMShubham Bajaj
06/04/2025, 2:23 PMthecurtis
06/04/2025, 3:39 PMthecurtis
06/04/2025, 3:39 PMthecurtis
06/04/2025, 3:59 PMthecurtis
06/04/2025, 11:39 PMVapi
06/05/2025, 12:48 AMthecurtis
06/05/2025, 3:00 AMthecurtis
06/05/2025, 3:02 AMVapi
06/05/2025, 10:42 PMthe time is {{"now" | date: "%b %d, %Y, %I:%M %p", "America/Vancouver"}} Canada/Vancouver time zone
This solution directly addresses the root cause by:
1. Using the proper LiquidJS syntax that VAPI supports for time zone-aware date formatting
2. Leveraging the existing time zone handling that's already built into the system (as shown in the test cases)
3. Using the correct IANA time zone identifier which is what JavaScript's Intl API expects
4. Avoiding the UTC hardcoding in the basic {{now}} variable