Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.

  • 1.  Failure Data Action in a Flow.

    Posted 05-28-2024 04:11
    No replies, thread closed.
    Hello,
    I have a trigger configured that triggers a flow, the purpose of it is to insert as an attribute of a conversation its own transcript.
     
    The flow is composed of 3 data actions.
    1. Get the communicationid based on the conversationid --> UI/Flow OK
    2. Obtain the url of the transcript --> UI/Flow OK
    3. Access the url and save the content in a variable --> UI OK-Flow Failure.
     
    The problem comes with this third data action, in the ui it works in 100% of the cases correctly, in the flow it goes through the failure branch 98% of the times.
     
    The problem is that in the performance of the data action, it shows that it executes correctly 100% of the time, without any error.
     
    This is my data action,

    Some help with that?
    BR
    {
  "name": "5.Get Transcript Messages ",
  "integrationType": "custom-rest-actions",
  "actionType": "custom",
  "config": {
    "request": {
      "requestUrlTemplate": "${input.url}",
      "requestType": "GET",
      "headers": {},
      "requestTemplate": "${input.rawRequest}"
    },
    "response": {
      "translationMap": {},
      "translationMapDefaults": {},
      "successTemplate": "{\"raw_json\": \"$esc.jsonString(${rawResult})\"}"
    }
  },
  "contract": {
    "input": {
      "inputSchema": {
        "type": "object",
        "properties": {
          "url": {
            "type": "string"
          }
        },
        "additionalProperties": true
      }
    },
    "output": {
      "successSchema": {
        "type": "object",
        "properties": {
          "raw_json": {
            "type": "string"
          }
        },
        "additionalProperties": false
      }
    }
  },
  "secure": false
}

    #ArchitectureandDesign
    #Integrations

    ------------------------------
    Adrian Rodriguez
    EOS Spain S.L.
    ------------------------------


  • 2.  RE: Failure Data Action in a Flow.

    Posted 05-29-2024 08:22
    No replies, thread closed.

    Most of us would need more info to give some feedback. Also, post in developers forum. 



    ------------------------------
    Matthew Raleigh
    Thermo Fischer CRG
    Sr. IT COMM Eng.
    ------------------------------

    Original Message


  • 3.  RE: Failure Data Action in a Flow.

    Posted 05-29-2024 12:58
    No replies, thread closed.

    Hi

    @Adrian Rodriguez, the data action that is failing is on the workflow? If it, on architect, you can use data action block, it give you 3 paths: sucess, failure and timeout. Also, it give you the option to caputre some values from data action execution:

    I suggest you to capture errCode, correlationId, entityName and userMessage at least then use "Set Conversation Data" to add the captured data as attributes. In this way you could get some hint to know why is it failing. 

    If you fail to find out what is wrong, just open a case with Genesys Customer Care and provide conversationId and correlationId, so they could help you to find out what is wrong.

    Regards,

    SG



    ------------------------------
    Saugort Dario Garcia
    Interacciones Inteligentes S.A.
    ------------------------------

    Original Message


  • 4.  RE: Failure Data Action in a Flow.

    Posted 05-30-2024 04:50
    No replies, thread closed.

    Hi!
    Thanks for your time!

    Yes, I did what you comment, it always goes down the Failure branch,
    Besides inserting it as participant data, I have configured a notification to send me by mail the steps it is following, when it reaches this point I receive that information but empty.
    This is an example. 

    I erased the conversation id for privacy. 

    Regards!



    ------------------------------
    Adrian Rodriguez
    EOS Spain S.L.
    ------------------------------

    Original Message


  • 5.  RE: Failure Data Action in a Flow.
    Best Answer

    Posted 05-30-2024 02:54
    No replies, thread closed.

    Hello Adrian,

    If you have a trigger that starts immediately when the conversation ends, it could be that the information isn't available in the API yet.

    Try setting Delayed Start on the Trigger, I usually wait 5-10 seconds which works unless there's an unusual delay with the APIs.



    ------------------------------
    Jan Heinonen
    Contact Center Specialist
    GlobalConnect AB
    ------------------------------

    Original Message


  • 6.  RE: Failure Data Action in a Flow.

    Posted 05-30-2024 04:52
    No replies, thread closed.

    Hi
    Thanks for your time!

    Ok, I will try with the delayed start.
    Now i'm working with some waits in the flow to wait X minutes in order to the transcription beign generated. ( 6 minutes)

    Regards!



    ------------------------------
    Adrian Rodriguez
    EOS Spain S.L.
    ------------------------------

    Original Message


  • 7.  RE: Failure Data Action in a Flow.

    Posted 06-03-2024 04:56
    No replies, thread closed.

    Hi,

    I changed the conditions on the trigger, now i'm executing these logic in the flow.

    It works better but in some cases doesn't work, i will keep investigating.

    BR.



    ------------------------------
    Adrian Rodriguez
    EOS Spain S.L.
    ------------------------------

    Original Message


Related Content