Basic workflows and actions in No-Code - Time & Space Complexity
When we look at basic workflows and actions, we want to understand how the time needed grows as we do more steps or handle more items.
We ask: How does the work increase when the tasks or inputs get bigger?
Analyze the time complexity of the following workflow steps.
Start process
For each item in list:
Check item status
If status is valid:
Perform action A
Else:
Perform action B
End process
This workflow goes through a list of items, checks each one, and performs one of two actions based on the check.
Look for repeated steps that take most time.
- Primary operation: Looping through each item in the list.
- How many times: Once for every item in the list.
As the list gets bigger, the number of checks and actions grows too.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | About 10 checks and actions |
| 100 | About 100 checks and actions |
| 1000 | About 1000 checks and actions |
Pattern observation: The work grows directly with the number of items.
Time Complexity: O(n)
This means the time needed grows in a straight line as the number of items increases.
[X] Wrong: "The time stays the same no matter how many items there are."
[OK] Correct: Because each item needs to be checked and acted on, more items mean more work.
Understanding how workflows scale helps you explain how your solutions handle growing tasks clearly and confidently.
"What if the workflow had two nested loops over the list? How would the time complexity change?"