Kit Visual Automations: entry, waiting and safe editing

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Check the builder version before following button instructions

Kit documents a legacy Active, Inactive and Paused model and a Visual Automations 2.0 beta using On, Off and Hold on entry. In those descriptions, the running state permits entry and progress; Off or Inactive blocks both; Paused or Hold on entry allows new entrants but holds progress. The beta also documents draft edits and a publish checklist. Inspect the builder in your account rather than assuming every screenshot has the same labels.

Our recommendation is to record the intended behavior in plain language: may new subscribers enter, and may existing subscribers advance? A single word such as paused is an inadequate change plan if the operator does not know both answers.

A fictional welcome-journey edit

Assume a creator wants to replace a resource link in a welcome journey while keeping new signups organized. Before editing, inventory controlled examples at the entry point, waiting in a delay and already beyond the email being changed. These positions require different expectations.

Decide whether new entrants may accumulate during the work or must be excluded entirely. That is a business choice. Review the actual builder state and publication controls before changing it.

A controlled change procedure

1. Identify the builder version and current live state.
2. List the entry mechanisms and the subscribers' current positions.
3. Record the exact intended content or logic change.
4. Select the appropriate entry-and-progress behavior for the maintenance window.
5. Review the draft or change preview supported by the account.
6. Validate controlled cases, then intentionally publish or resume as applicable.
7. Reconcile existing waiting subscribers separately from new entrants.

Do not assume edits are retroactive

Kit's editing guide notes that subscribers who already passed a new step do not go back through it automatically, and existing holders of a newly selected tag entry point do not automatically enter just because the entry point was added. Our operational recommendation is to define any reprocessing cohort explicitly rather than assuming a diagram edit reruns history.

Also check whether reused sequences are shared. Duplicating a diagram is not proof that every underlying content resource became independent. Inspect references before editing a copy intended only for a trial.

Diagnose waiting with an expected state

Our troubleshooting worksheet records subscriber ID, observed node, expected next step and the condition required to move. Waiting may be intentional: a declared date or event can hold progress even when the automation is running.

Do not remove and re-add a large group solely to clear a waiting count. Establish which external messages or actions already happened and design recovery around that evidence.

Acceptance criteria

Accept the change when the intended builder version is identified, new and existing controlled subscribers behave as declared and no group is reprocessed by accident. Keep a short change record with the expected impact and owner.

This guide provides a version-aware operating procedure, not a live Kit test or a promise that beta behavior is fixed. Recheck current official documentation and the account's displayed controls before changing a live journey.