https://vapi.ai/ logo
Join Discord
Powered by
[Blocks] [Human required] Tool variables not getti...
# support
z
Hi everyone, and happy new year! I'm facing the problem where the variables set with the liquid language template aren't getting replaced, and instead, I'm getting the raw text on the called endpoint. This only happens with the Tool block, and only on the inputs. Nevertheless, I've found out that if for some reason, the agent tries again to call the tool, from the second time onwards it fulfils the variables properly, it only happens the first time. The problem is that we need the value filled the first time the tool is called, not the second one. For example, if the JSON body is:
Copy code
json
{
  "order_number": "{{ask_order_number.output.order_number | default: -1 }}"
}
Then the first time is called we receive on the server this exact block, without any replacements. The second time we receive:
Copy code
json
{
  "order_number": "8888"
}
Although the real value was set before the first call, as a previous conversation block did replaced the exact template correctly. I've seen other people complain about the same issue, so I hope that this post clarifies a bit of what might be the problem. Please don't hesitate to ask me anything about it, I will try my best to point out the exact problem. > I've already asked it here: https://discord.com/channels/1211482211119796234/1324353725564715121 but the post was locked as solved altough it wasn't. It requires human support, but the post was locked so nothing else could be done. I've recreated it looking for human help. Best regards, Antonio
v
message has been deleted
@ZamJAM Hello Antonio, and Happy New Year to you too! I'm sorry to hear about the issue you're experiencing with the liquid language template variables not being replaced correctly on the first call within the Tool block. It's great that you've provided a detailed description of the problem, and I understand how important it is for the variables to be filled correctly from the first attempt. This issue seems to be quite specific and might require a closer look into how the Tool block is handling the liquid template variables. Since you've mentioned that other people have experienced similar issues, it could be indicative of a bug or a need for a more detailed explanation on the expected behavior of the Tool block when processing templates. Given that you've already reached out on Discord and the issue wasn't resolved to your satisfaction, I would recommend reaching out to the support team again with the details you've provided here. They may need to investigate further or escalate the issue to the development team for a fix. In the meantime, if there's anything else I can assist you with or any other information you'd like to provide, please let me know. I'm here to help! Best regards, VAPI Support Bot
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
z
Hi @User, I recommend you checking the linked post, as it contains a bit more of information. Please let me know if I can help in any way! Best regards, Antonio
s
@ZamJAM as of know Vapi Blocks is not ready for development and production use and we are working on make it ready to use pretty fast.
z
Hi @Shubham Bajaj , We didn't knew that it wasn't ready for development. We saw that it was on Beta, but that most of the things were in place. Nevertheless, this is a bug to be addressed as it reduces the blocks capabilities by 1/3 (One of the block types is not usable). In our case is all we need to start testing properly, are there any plans already for the fix or any estimate? Best regards, Antonio
s
@ZamJAM We are reworking on BLOCKS, and as of now ETA is till march.
2 Views
PreviousNext
Powered by