Rules & Best Practices

To ensure your automation runs smoothly and your WhatsApp number remains healthy, there are a few critical system rules you must follow when designing your flows.

1. The 20-Second Execution Limit

Our system enforces a strict time limit on how long a flow can run in the background between user interactions.

• The Rule: Any sequence of actions must complete within 20 seconds. If the system is still “working” (processing logic, APIs, or waiting) after 20 seconds, the flow is automatically cancelled.
• Crucial Note on Timers: The Timer (Wait) block counts toward this limit.
  • If you add a 10 second wait, the system keeps the connection open for those 10 seconds.
  • This leaves you with only 10 seconds of remaining processing time for other blocks in that sequence.

2. Flow Conclusion & Reset

Understanding when a flow “stops” is key to building good experiences.

• Open-Ended Nodes: If a block (like a Message or Logic node) has no connection coming out of it (no target), the system automatically attaches an invisible End Block.
• Effect: Reaching this end point immediately stops the 20-second timer and concludes the execution.
• Cursor Reset: Once the flow ends (either by hitting an end node or timing out), the “User Cursor” resets. This means the next message the user sends will trigger the flow from the very beginning (The Trigger Block).

3. Avoid Infinite Loops (Spam Protection)

It is possible to connect blocks in a circle (e.g., Block A → Block B → Block A). However, creating a “tight loop” without user interaction is dangerous.

• High-Speed Execution: The system is fast. Without a stop, it can theoretically calculate and queue up to ~200 messages per second.
• The Consequence: If you create a loop that runs for the full 20-second limit, you could generate thousands of messages instantly.
• Result:
  1. The system will hit the 20-second limit and kill the flow.
  2. If any messages were sent, WhatsApp will likely block your number for spamming behavior.