Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.

  • 1.  acw topic trigger bug?

    Posted 02-08-2023 09:04
    No replies, thread closed.
    Created a trigger for acw topic which was failing.

    Through removing fields one at a time I have seen what causes the error.

    Basically the field wrapupNotes causes the schema error. If I remove that field from my input variables the workflow works as expected.
    I know case sensitive etc, checked all of that.
    Is this a bug, has anyone else tried using this field?

    As a side, the eventTime integer field in topic schemas, what is this a measure of, not found any documentation that explains that fields value and how to get to a datetime?


    Triggers in general...
    Painful process to troubleshoot with no Audit entries for these failures and the inbuilt errorCode fields only states INVALID_SCHEMA and the detailsErrorCode is just as unhelpful as always states ACTION.PROCESSING.

    Also with the workflow, even if I unpublish, and remove trigger that references workflowId I am still unable to remove variables from the Flow as architect still flags them as in use by a published flow.
    I have to create new version workflow, get new ID and re-create the trigger each time troubleshooting schema issues.

    Simon


    #ArchitectureandDesign

    ------------------------------
    Simon Brown
    Maintel Europe Limited
    ------------------------------


  • 2.  RE: acw topic trigger bug?

    Posted 04-28-2023 12:38
    No replies, thread closed.

    Did you get an answer for this? Perhaps via Support case?



    ------------------------------
    George Ganahl GCP (Genesys Cloud), CCXP
    Principal PS Consultant
    Genesys
    ------------------------------

    Original Message


  • 3.  RE: acw topic trigger bug?

    Posted 05-09-2023 12:33
    No replies, thread closed.

    Hi,

    Delayed response, been on vacation.
    I did not get an answer to this, did not raise a support case at the time.

    I understand the timestamp now, unix time in seconds so that's fine.
    I can also get a more meaningful message using the message property from call when trigger fails.

    As for the missing field on the acw schema, I have not checked any further. Right now, getting notes from the trigger is not a requirement for the customer.
    It is an observation that the trigger fails even though its shown in the schema, adding as Input to workflow is instant error which is why asked the question.

    Using triggers for conversation notifications to a customers own system is working ok at present. Shame customer.end does not have the divisionId in the schema though. I had to implement an /api to get the division for the topic from the conversationId.
    Looking forward to some form of Admin UI for triggers to view/monitor and audit better!

    Regards
    Simon



    ------------------------------
    Simon Brown
    Maintel Europe Limited
    ------------------------------

    Original Message


Related Content