Skip to main content

 

 

 

 
Language:

 

 
Service Studio version:
 
 
OutSystems

Invalid Action Flow Error

Template:OutSystems/Documentation_KB/ContentCollaboration
  • Edit
    Collaborate with us
    Edit this page on GitHub
  • The Invalid Action Flow Error is issued, for example, when you create logic flows for Screen Actions, Client Actions, Server Actions, or Data Actions.

    Double-click on the error line in TrueChange to take you directly to the Action that is issuing the error.

    'Cycle' path must return to the 'For Each' element in <action>

    Cause

    You have a For Each element with a Cycle loop path that does not return to the For Each element.

    Recommended action

    Update the Cycle loop to return to the For Each element in your Action.

    For example, for a list, you need to create a connection from the last step in your logic to the For Each node to close the cycle.

    More info

    For information about creating Screen, Client, Server, and Data Actions, see Actions in Reactive Web and Mobile Apps and Actions in Web Applications.

    Ambiguous paths to <element> in <action>

    Cause

    You have an element that belongs simultaneously to different Start, Exception Handler, or For Each paths.

    Examples

    Flow Description
    In this situation, the Assign element belongs to the Action flow and also to the Exception flow, therefore the Error Handler flow is crossing the regular execution of the Action.
    In this situation, the Assign element belongs to the Action flow and also to the For Each flow.

    Alternatively, there are missing paths in a node of your Action. For example, you have a For Each node with no Cycle loop path.

    Recommended action

    Edit the Action flow and update the ambiguous paths. Add any paths that are missing, for example, from a For Each node.

    Check Exception Handler for information about how to add an Exception Handler element and its logic in your Action flow.

    More info

    For information about creating Screen, Client, Server, and Data Actions, see Actions in Reactive Web and Mobile Apps and Actions in Web Applications.

    Check Exception Handling Mechanism for additional information about Exception Handler flows.

    Cause

    You have an If element in your Action that does not have a True link and a False link.

    Recommended action

    Update the If element in the Action to have True and False branches.

    More info

    For information about creating Screen, Client, Server, and Data Actions, see Actions in Reactive Web and Mobile Apps and Actions in Web Applications.

    Switch condition for <path> connector must return a 'Boolean' value

    Cause

    You have a condition in your Switch element that does not return a Boolean value.

    Recommended action

    Update the Switch element in the Action to have the condition return a Boolean value.

    More info

    For information about creating Screen, Client, Server, and Data Actions, see Actions in Reactive Web and Mobile Apps and Actions in Web Applications.

    <switch> must have an otherwise optional connector in <action>

    Cause

    You have a Switch element in your Action that does not have the Otherwise path.

    Recommended action

    Update the Switch element in the Action and add an Otherwise path.

    More info

    For information about creating Screen, Client, Server, and Data Actions, see Actions in Reactive Web and Mobile Apps and Actions in Web Applications.

    Start is required in <action>

    Cause

    You have an Action flow that does not have the Start element.

    Recommended action

    Edit the Action and add a Start element. An Action flow must have only one Start element.

    More info

    For information about creating Screen, Client, Server, and Data Actions, see Actions in Reactive Web and Mobile Apps and Actions in Web Applications.

    More than one Start found in <action>

    Cause

    You have more than one Start element in your Action.

    Recommended action

    Edit the Action and remove the additional Start elements.

    More info

    For information about creating Screen, Client, Server, and Data Actions, see Actions in Reactive Web and Mobile Apps and Actions in Web Applications.

    • Was this article helpful?