Hi Go HighLevel Team 👋

I’d like to propose an improvement to how execution control and re-entry logic work inside Advanced Workflows.

## 🚨 Current Situation

Right now:

* If a contact is already inside a workflow, new trigger events are ignored.

* Re-entry behavior is controlled at the workflow settings level via “Allow Re-entry.”

* We cannot control execution behavior at the individual trigger level.

This creates limitations, especially for conversational and interactive automations.

---

## 💬 Real Use Case

Example scenario:

I send a message saying:

> “Reply to this message or click the link below.”

Then I use:

* , or

* A

to continue the workflow.

If the contact replies again later or clicks again while still inside the workflow, the trigger does nothing.

In conversational automations, this breaks flexibility and forces us to build workarounds.

---

## 1️⃣ Add Trigger-Level Execution Control

Each trigger should have an option like:

✅

When enabled:

* The system ends the current active execution.

* The new trigger proceeds.

* The workflow starts at the configured trigger entry point (not necessarily the beginning).

This would allow true conversational resets and dynamic behavior handling.

---

## 2️⃣ Move Re-Entry Control to Trigger Level

Instead of having “Allow Re-entry” at the workflow settings level, move execution control directly to each trigger.

Each trigger could have options like:

* ☐ Allow multiple entries through this trigger

* ☐ Stop current execution and re-enter from here

This would:

* Provide granular control per entry point

* Avoid conflicts between different triggers in the same workflow

* Reduce the need for duplicate workflows

* Simplify architecture

* Make behavior more predictable

---

## 🎯 Why This Matters

Advanced Workflows are powerful — but execution control is still too global.

Moving re-entry and execution management to the trigger level would:

* Improve conversational automation

* Enable cleaner interactive flows

* Support complex SaaS and agency use cases

* Reduce workaround logic

* Make workflows more modular and scalable

This change would significantly improve workflow state management and flexibility across the platform.

Would love to hear the team’s thoughts and see if this could be considered for the roadmap 🙌🚀