Hello, 

Microflow Example:

1. User Action: User clicks on "Update Profile" button.
2. Microflow Execution:
   • Microflow retrieves the user's current information from the database.
   • User is prompted to enter new information (like name or email).
   • After user submits the changes, microflow updates the database with the new information.
   • Finally, microflow sends a success message to the user.

In this example, the microflow handles all the steps in sequence—from retrieving data, prompting for updates, saving changes, to displaying feedback—all before completing its execution and showing the final result to the user.

Nanoflow Example:

1. User Action: User clicks on "Update Profile" button.
2. Nanoflow Execution:
   • Nanoflow starts immediately when the user initiates the action.
   • As the nanoflow progresses, it might fetch some initial data from the database.
   • It displays a confirmation message to the user.
   • It updates the user's profile information in the database.
   • It might display a success message or redirect the user to another page right away.

This difference in execution style makes nanoflows suitable for tasks where immediate client-side actions or feedback are needed, while microflows are used for more complex workflows that require sequential processing and final outcome delivery.

Hope this helps!

Hi Gain 

When a nanoflow steps through its actions, client actions are directly executed. This is different from client actions in a microflow, which only run when the client receives the result from the microflow. For example, an open page action immediately opens a page in a nanoflow, instead of waiting until the end as it does in a microflow. Thus, in a microflow, the page will only open once the microflow has completely executed