Please see assistant id 03555353-b9ea-4825-b5fc-6102b84dc756 example call id 019a074e-1e13-7ff4-9b17-2253d85954a5 the liquid js is not rendering, but when i put it in to the liquid js renderer on liquidjs.com , it is rendering correctly. Please advise how to fix, or implement fix on your end.

Suggestion: Double-check that your prompt uses double curly braces and the correct LiquidJS syntax, and that all required variable values are passed in your API call. For example:

text
Hello, {{"now" | date: "%A, %B %d, %Y, %I:%M %p", "America/Los_Angeles"}}

If the variable is not set via the API or call configuration, it will not render in Vapi—even if it works on liquidjs.com. See the [Dynamic Variables documentation](https://docs.vapi.ai/assistants/dynamic-variables) for details. Source: - [Dynamic Variables documentation](https://docs.vapi.ai/assistants/dynamic-variables)

Additionally , for this call log: 019a0776-cf29-7ddb-a181-e266fd1158a0 We called an assistant that had previously been working, and now it is not. I believe you have had a regression in your liquid js templating and it is not not evaluating correctly for assign variables. Please fix - we need this badly and cannot really use the product without it for our use case

bump on this. This is happening to us as well. Injected assistantOverrides.variableValues from the create chat endpoint are also not rendering. This was semi-reliable prior to ~October 15

@Matt C thank you for adding - confirms I’m not crazy.

Thanks for flagging this. We will test now and provide an update

I provided the specific information on the support email chain thats going on - moving it to that