After some digging I discovered something. This error happens when occurrence API returns 400 Bad Request error. This led me to identify two scenarios in which it can happen:
1. When a query is sent while another query is being processed, it consistently triggers a 400 bad request error. Subsequent queries also yield the same error code.
2. Although less common, random queries can sometimes result in a Bad Request error. I do not know how helpful this information is, but I can provide the chat_id associated with the instance: 677cfad3-5084-40d0-81d0-08592b5927f5.
1. When a query is sent while another query is being processed, it consistently triggers a 400 bad request error. Subsequent queries also yield the same error code.
2. Although less common, random queries can sometimes result in a Bad Request error. I do not know how helpful this information is, but I can provide the chat_id associated with the instance: 677cfad3-5084-40d0-81d0-08592b5927f5.