| Table of Contents |
|---|
Global Errors
...
UChat also offers add-on to increase the timeout limits, the cost is $20 per month to increase 10 seconds more. You can stack on the add-on. You can find more about it here:
https://uchat-com-au.atlassian.net/wiki/spaces/UKB/pages/731676673/Bot+Add-Ons#OpenAI-Timeout-Period
Error: “Data Store Error: Connection is not verified”
...
To resolve this, make sure that the body of the notification is not blank. If the body consists out of a custom field then check the bot user to see if that custom field populated properly.
Error: “Broadcast failed, Bot user unsubscribed”
...
There can be several other reasons as well. This could happen if you installed a template and the google sheet was not copied to your own account.
This can happen if your workspace does not have google sheets integrated yet and thus the installation of the template was not able to install a copy of the used google sheet to your account
Make sure you connect your Google account in Integration -> Data/File Storage, and also select the correct spreadsheet in the Google sheet action.
...
The UChat servers time out after 15 seconds. The solution is to make sure the API call is completed within 15 seconds. If you want to increase this limit, you can do so by purchasing an add-on here:
Note: You can handle this error within your flow using the response code “0”
...
You can purchase the timeout expansion here:
https://buy.stripe.com/9AQbJR2qveTC4N2fZf
Please note, it’s $20 per month for every 10 seconds extra. The add-on is at the bot level. For example, if you want to increase the limit by 30 seconds, then change the quantity to 3 from the above payment link and it will cost you 60$ per month.
...
If you are using a user custom field - variable in the card title, you will need to make sure the variable has the value. you can check this by looking at the bot user overview and select the bot user which has the error triggered for. Ensure that the custom field used for the card title has any value. If not then it means your steps before this node have an issue you need to troubleshoot somewhere
...
Otherwise, you will see the error. If you are using a user custom field in the card title, you can use the condition check before sending the card, and notify the admin if there is any issue like this.
...
First of all, Only support the tables with auto-increment primary key id
Also, Once the table is synced to UChat, we don’t delete the synced table even if it's deleted in your Postgresql database.
...
500/day - Included -› 15K requests/per month
1000/day - $20 per month -› 30K requests/per month
2000/day - $40 per month -› 60K requests/per month
3000/day - $60 per month -› 90K requests/per month
4000/day - $80 per month -› 120K requests/per month
5000/day - $100 per month -› 150K requests/per month
10000/day - $200 per month -› 300K requests/per month
Payment link:
https://buy.stripe.com/00g9BJ6GLcLugvKbIV
You can select how many add-on they want to purchase, and every unit means 1000 requests per day, cost is $20 per month.
...
Important note, the title can’t be saved in Hebrew as it will throw an error when importing. So save the title in English format.
Error: “Comment reply error. We've limited the number of times you can post, comment, or do anything else to prevent spam. You can try again later”
This issue is caused if you have high traffic on your Facebook page post comment wise and the chatbot is actively responding to each comment. In order to prevent your page from being flagged by Meta there is a rate limit implemented to prevent that.
In order to resolve this issue you can do either of the following two options”
OPTION 1:
if you reply directly with static replies from the comment keyword trigger you can use our built-in solution to delay the chatbot replies with random intervals.
On the right you will have the option to set a random delay. We advise the higher the traffic the higher the random reply interval. You have options from several minutes up an hour
OPTION 2:
If you use a flow to reply to the user’s comment then consider setting up a split node with several sequences connected.
This is how a flow could look like
You start the flow with a split node then connect each variant to its own action node with a different add to sequence
Each sequence will basically point to the exact same flow where you have the comment reply action set up but on the sequence itself you can determine how long to wait before the flow is triggered
This way you have more flexibility and prevent posting instantly