Automate

 View Only

  • 1.  WFAssignment.Frozen error in Workflow

    Posted 01-05-2022 06:14
    Hi All,

    Winshuttle Evolve 20.1:
    After an approval of a approval element I get the error "WFAssignment.Frozen".
    Other parts of the workflow with the same setup are working fine.
    Does anyome have an idea how to solve this?
    Searched for it on Winshuttle sites and Internet but couldn't fine any information about this.

    Kind Regards.

    ------------------------------
    Jan van Asseldonk | Consultant
    CTAC | +31629078169
    ------------------------------


  • 2.  RE: WFAssignment.Frozen error in Workflow

    Posted 01-06-2022 01:59
    I've entered a support ticket for this now.

    ------------------------------
    Jan van Asseldonk | Consultant
    CTAC | +31629078169
    ------------------------------

    Original Message


  • 3.  RE: WFAssignment.Frozen error in Workflow

    Employee
    Posted 01-06-2022 09:33
    Hi Jan
    Sorry I didn't get a chance to reply yesterday.  I would recommend the same.  I looked through the ticketing system and didn't see anything similar.  The only thing I would wonder, is this a group assignment?  Did someone else in the group open the task and lock it, so that you cannot complete it?  Just a thought.
    Best Regards,
    Sigrid

    ------------------------------
    Sigrid Kok
    PSE | Winshuttle NA
    ------------------------------

    Original Message


  • 4.  RE: WFAssignment.Frozen error in Workflow

    Posted 8 days ago

    Did this ever get resolved? If so, can you explain how? I am getting the same message. Thx



    ------------------------------
    Chase Shifflett
    Dominion Energy, Inc.
    Richmond VA
    ------------------------------

    Original Message


  • 5.  RE: WFAssignment.Frozen error in Workflow

    Employee
    Posted 8 hours ago

    Hi Jan,

    The error "WFAssignment.Frozen" typically occurs under the following conditions:

    • There are no active assignments, while the process status remains Running, or

    • A task does not resolve to any Actor, while the process is still in Running status.

    In some cases, the issue is caused by an incorrect decision node and its transition conditions. After completion of an approval element, the transition logic may fail to return a valid next activity node. As a result:

    • No new assignment is created,

    • The process remains in Running state,

    • The system detects a deadlock situation and triggers the WFAssignment.Frozen error.

    Resolution

    To resolve this issue, please:

    • Validate all transition conditions associated with the decision/approval node.

    • Ensure that at least one valid next activity node is returned after the decision node/ transition condition/ approval action.

    • Confirm that proper Actor mapping is configured for the subsequent task.

    Once the workflow logic is corrected and redeployed, the process should proceed without entering a Frozen state.


    Thanks



    ------------------------------
    Divya Verma
    *Precisely Software Inc.
    ------------------------------

    Original Message