Genesys Cloud - Main

 View Only

Discussion Thread View
Expand all | Collapse all

Execution data flow level changed today after Application republishing

  • 1.  Execution data flow level changed today after Application republishing

    Posted 01-13-2025 15:14

    Hi all, 

    today we noticed that application with flow size 75-80 % got execution data level changed from 'All'

    to 'Base' after republishing.

    It happen to any application which currently work with level ALL and republished. For testing purpose we reduced app size from red to yellow (61%). Execution data flow level remain Base.

    In Architect each of those apps have Execution data flow level set to ALL.

    I also see that some release notes were added today, but there is nothing regarding subject.

    Thanks


    #ArchitectureandDesign
    #Implementation

    ------------------------------
    Vitalii Hetman
    Genesys Professional Services Engineer
    ------------------------------


  • 2.  RE: Execution data flow level changed today after Application republishing

    Posted 01-14-2025 16:21

    Hello Vitalii,

    As far as I'm aware, there were no changes to Architect for this weeks changes. Are you able to see if there were any other edits made to the flow version?



    ------------------------------
    Jason Kleitz
    Online Community Manager/Moderator
    ------------------------------



  • 3.  RE: Execution data flow level changed today after Application republishing
    Best Answer

    Posted 01-14-2025 17:34

    A recent change restricts the execution data level to base when a call flow has more than 350 variables.  This was done to prevent a bug that caused your flow to go into event handling.  This only affects inbound call, outbound call, inqueue call, secure call, and voicemail flows.



    ------------------------------
    Melissa Bailey
    Software Engineer
    ------------------------------



  • 4.  RE: Execution data flow level changed today after Application republishing

    Posted 01-14-2025 17:49

    I have a flow with only 220 variables, and level was also changed to base. I have system level set to all, and I tried individual flow execution data change to all, yet all call flow executions are still only base level starting today.



    ------------------------------
    Adrian Torres
    Voip Network Engineer
    ------------------------------



  • 5.  RE: Execution data flow level changed today after Application republishing

    Posted 01-15-2025 04:57

    check the number of variables in shared modules that are called from your main app



    ------------------------------
    Vitalii Hetman
    Genesys Professional Services Engineer
    ------------------------------



  • 6.  RE: Execution data flow level changed today after Application republishing

    Posted 01-15-2025 04:54

    Hi Melissa,

    and thank you for the clarification! now it make sense! At least we understandwhat need to be optimized to get detailed log again!



    ------------------------------
    Vitalii Hetman
    Genesys Professional Services Engineer
    ------------------------------



  • 7.  RE: Execution data flow level changed today after Application republishing

    Posted 02-06-2025 18:11

    Thanks. Is this a temporary measure while the bug is being fixed and will be removed at a later date, or is it expected that we will have to build around this limitation as it will be permanent?



    ------------------------------
    Jeremy Carlton
    SoFi Technologies, Inc.
    ------------------------------



  • 8.  RE: Execution data flow level changed today after Application republishing

    Posted 02-06-2025 18:20

    Hopefully temporary.  



    ------------------------------
    Melissa Bailey
    Software Engineer
    ------------------------------



  • 9.  RE: Execution data flow level changed today after Application republishing

    Posted 10 days ago

    Hi @Melissa Bailey

    Am I correct to say that the issue is still occurring, and that a fix has not as yet been identified for the Execution History issue?

    I ask, as I only tripped on to this yesterday, and can see that it is still occurring, at least from our perspective.

    I understand the Variable Count Threshold, and is is MORE than likely going to be the case for us, as our flows are VERY complex, and by no means simple. Asa a result, trimming the number of variables down will be anything BUT simple.

    Assuming that the bug is still under investigation, is there an ETA as to when this is likely to be resolved?

    Your feedback would be most appreciated.

    Cheers,

    Catelyn



    ------------------------------
    Catelyn Hearne
    ------------------------------



  • 10.  RE: Execution data flow level changed today after Application republishing

    Posted 9 days ago

    Yes it's still occurring.  No there is not an ETA for a different solution.



    ------------------------------
    Melissa Bailey
    Software Engineer
    ------------------------------



  • 11.  RE: Execution data flow level changed today after Application republishing

    Posted 01-15-2025 04:54

    We're also encountering this "issue". I was testing yesterday and even though the Execution Data level was set to All (or Verbose Notes), some flows would only log Base level data. Very frustrating.

    We aren't over 350 variables so shouldn't be being limited by that.



    ------------------------------
    James Dunn
    Telecoms Specialist
    ------------------------------



  • 12.  RE: Execution data flow level changed today after Application republishing

    Posted 01-15-2025 04:56

    are you taking in account variables in shared modules that are used by your main app? Our app has only 86 variables but because of numerous shared module we could exceed threshold easily



    ------------------------------
    Vitalii Hetman
    Genesys Professional Services Engineer
    ------------------------------



Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources