Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

In this section, you will find troubleshooting instructions for resolving potential issues.

Chat not working or synchronization error

Issue: If you are experiencing issues with chat functionality or synchronization errors, the problem may be related to the BeesenderOperatorToken and BeesenderOperatorAppId system settings.

Solution:

To troubleshoot this issue, follow these troubleshooting instructions:

  1. Verify that the values of the BeesenderOperatorToken and BeesenderOperatorAppId system settings match and correspond with each other.

  2. Ensure that there are no checkmarks (checkboxes) enabled for either of these settings.

  3. Confirm that both settings have a token value without spaces at the beginning or end of the token-containing string.

Synchronization error

400 Error during Synchronization

If you are using a Creatio demo environment, it is likely that this error means that the limit of records in one of the system tables has been reached.

First, check the number of records in the BeesenderLog table. To do this, run the following SQL query:

 SELECT COUNT(*) FROM "BeesenderLog"

If you see that the number of records has reached 1000, feel free to delete them by running the following query: 

 DELETE FROM "BeesenderLog"

401 Error during Synchronization

To resolve the 401 error during synchronization, it's often necessary to verify the accuracy of the login and password in the "Beesender chat configuration" section. It's recommended to re-enter the login and password, save the changes, and then synchronize again to ensure they're properly updated.

404 Error during Synchronization

If you encounter a 404 error during synchronization, there may be two reasons for its occurrence:

Issue 1: The package methods have not been published.

Solution:

  1. Navigate to the system designer.

  2. Select Advanced Settings.

  3. Click on Compile on the opened page.

  4. Wait for the compilation process to finish.

  5. Verify that the compilation was successful.

Issue 2: Your CRM system server cannot find our service.

Solution:

Please ensure that your service has access to the resource specified in the BeesenderOperatoHost system setting.

500 Error during Synchronization

If you encounter a 500 error during synchronization, there may be two reasons for its occurrence:

Issue 1: Beesender service is unable to connect to your CRM system.

Solution:

If you are experiencing this issue, it may be that our service is unable to connect to your CRM system. Please click on the "Synchronize" button while in your CRM system at the address that our service can connect to.

Issue 2: BPMCSRF token option is disabled in your system

Solution:

  • If you are using an On-site system, contact your IT specialists and request that they enable the BPMCSRF token option in the CRM system settings on the server.

  • If you are using a Cloud system, contact Creatio technical support and request that they enable the BPMCSRF token option for your system.

0

If you encounter a 0 error during synchronization, there may be two reasons for its occurrence:

Issue 1: Your system server cannot find the Beesender service.

Solution:

If you encounter issue #1, please ensure that your service has access to the resource specified in the BeesenderOperatoHost system setting.

Issue 2: Unstable internet connection.

Solution:

If you encounter issue #2, it may indicate an unstable internet connection. Please try again later.

Chatbot Getting Stuck on Beesender: Button message Element

Issue: Chatbot gets stuck on the Beesender element with message buttons and does not send the message to the chat.

Solution:

  1. Go to the Studio workplace and open the System Settings section, or navigate to the System Settings section from the system designer.

  2. In the filter, select Code and enter the value UsePerformerCultureInUserTask.

  3. Open the found setting and uncheck the checkbox.

To restart the site:

  • If you are using Creatio Cloud, submit a request to Creatio technical support to reboot your system.

  • If you are using Creatio On-site, contact the IT specialists in your company and request a system reboot.

Empty Agent Panel

Issue: If the agent panel appears empty and no labels or icons are visible, it may indicate that static content is not enabled in the system.

Solution:

To resolve this issue, please contact Creatio technical support and request that static content be enabled. Specifically, ask for the "UseStaticFileContent" flag to be turned on.

  • No labels