AppWorx, Dollar Universe and Sysload Community

  • Private Community
 View Only
Back to discussions
Expand all | Collapse all

Unexplained Uproc n° change caused his successor to go into a refused status

  • 1.  Unexplained Uproc n° change caused his successor to go into a refused status

    Posted Oct 27, 2020 11:15 AM
    Hello,

    I have recently seen an odd behavior in my production, and i would like to have some feedback about this.

    I have this uproc called PE_EXP_XDN that waits for the completion of PE_EXP_XA1. So far so good.

    Things starts to get interesting when PE_EXP_XA1 gets its first condition, it changes his uproc n° causing PE_EXP_XDN to go in refused status. I have never seen this kind of behavior. Does anyone know what configuration could cause this?



    Thanks for your help/feedback !


  • 2.  RE: Unexplained Uproc n° change caused his successor to go into a refused status

    Posted Nov 04, 2020 04:18 PM
    Hi,

    Beware of a fixed feature
    A wait event can become Refused when the conditionned Uproc is not there (not only on the corresponding MU , but also locally)

    The resolution is
    * only to push the conditionned Uproc locally
    * An a node var setting to have the "as before" behavior (I let you check on the documentation/RLN to know which it is)

    Perhaps help.
    Regards
    Original Message