Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Error handling when using Genesys global function

  • 1.  Error handling when using Genesys global function

    Posted 06-05-2025 18:37

    IvanDg | 2023-06-13 06:22:26 UTC | #1

    Hello I have the following 2 error use cases and I wanted to know what is the best way to handle this.

    1. Error getting script to genesys.min.js (for some reason the server serving the script is down)
    2. Error on starting web messaging. (for some reason the server is down/message deployment was deleted)

    I wanted to handle above cases and show a customized message. But upon checking it is not throwing any error. It is just logging a console.

    IvanDg | 2023-06-14 03:13:06 UTC | #2

    Updates on this

    1. I have fixed this by listening to error event when loading the js file
    2. I am not sure if this is a bug on the script side, but when I tried to input a deploymentId that does not exist it shows the following error which I feel should be more related to 'deployment id does not exist' and then throw an exception error.

    loadJSON failed with status code: 403

    Angelo_Cicchitto | 2023-06-14 11:40:50 UTC | #3

    Thanks, we'll revisit your suggestion.

    IvanDg | 2023-06-15 06:05:22 UTC | #4

    Hi Angelo,

    So that means there is no way we can handle errors using the Genesys global function right now am I right? Sample use cases:

    1. Deployment ID does not exist
    2. After connecting successfully and starting a conversation, for some reason there is an error calling Messaging Service Commands

    Thanks!

    system | 2023-07-15 06:05:38 UTC | #5

    This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 20399



Related Content