How Tags Start and Stop Automation in Gemini HQ

What’s happening

In Gemini HQ, automations start, pause, or stop based on tags being added or removed.

When a tag changes, the system immediately checks whether a workflow should begin, continue, or exit.

This can look sudden, but it’s intentional behavior.

Why this happens

Tags are not labels. They are control signals.

Workflows in Gemini HQ are built to “listen” for specific tags. When the condition is met:

• A workflow starts

• A contact enters a new path

• A contact is removed from a workflow

• A step is skipped by design

This keeps automations precise and prevents contacts from receiving messages that no longer apply.

What to check

Before assuming something is wrong, review these items carefully:

• Tag spelling matches exactly (tags are case- and character-sensitive)

• The tag is applied before the workflow trigger expects it

• The workflow trigger is set to Added, Removed, or Exists correctly

• No conflicting workflows are using the same tag as an exit condition

• The tag is not being added and removed too quickly by another automation

Most issues trace back to timing or trigger configuration, not system failure.

What this does NOT mean

This does not mean:

• Automations are firing randomly

• Contacts are frozen or stuck

• The system is losing data

• A rebuild is required

Gemini HQ is doing exactly what the workflow rules instruct it to do.

When to contact Support

Contact Support if something is not functioning as intended within your plan’s defined scope.

For next steps, review the Gemini HQ Support Center and Support Policies, as support availability and response scope vary by Support Plan.

© Copyright 2026 GEMINI HQ | All Rights Reserved