GitGlow 2.0 guide

Troubleshoot GitGlow

Recover from stale previews, missing repositories, connections, conflicts, and partial data.

Reviewed for 2.0Updated September 13, 2026
On this page

What this helps you do

Recover from stale previews, missing repositories, connections, conflicts, and partial data.

Find it in GitGlow

Start from the error message or unavailable-state action shown in the current screen.

Before you start

Recovery actions depend on the workflow; GitGlow preserves entered text and repository context whenever possible.

Steps

  1. Read the exact state and repository or connection identity.
  2. Use the offered Refresh, Reconnect, Continue, Abort, or Review recovery action.
  3. Verify the visible result before repeating a mutation.

Expected result

The workflow either returns to a reviewable state or presents a narrower actionable blocker.

Controls

The controls for this workflow appear in the steps above. Their availability follows the repository, connection, and edition requirements on this page.

Recovery

If the workflow cannot continue

Never blindly retry an ambiguous remote publication. Read current refs or provider state first.