Breadcrumbs

Preview runs of sequences

Before adding sequences to a timeline, preview them individually.

Running a Preview

  1. Ensure your desired Data Item is checked in the sequence header.

  2. Select AD User credentials if applicable.

  3. Choose the region (for example, North Europe or East US).

  4. Click Preview.

Go displays live feedback:

  • Execution progress per step

  • Response times

  • Error counts

  • Validation results

Preview mode helps verify that all steps, variables, and data items behave as intended before being orchestrated into a Timeline.

Clearing an AD user session before a preview run

If an Active Directory (AD) user assigned to a sequence has cached credentials from a previous run, you may need to clear that session state before running a fresh preview. This is most useful when testing a login flow end-to-end, reproducing an authentication failure, or verifying that a script handles a clean session correctly.

How to reset the session

  1. Open the sequence in the sequence editor.

  2. Locate the AD user dropdown in the sequence-level toolbar at the top of the editor.

  3. Click the Reset button adjacent to the selected user.

Leapwork Go immediately purges the cached backend cookie for that user. The next preview run will perform a full authentication handshake from scratch, without relying on any previously stored session state. This matches the reset behaviour available in the AD Users data item.

Button availability and states

The reset control changes state depending on the current context.

State

Condition

Active

A valid AD user is selected in the dropdown

Disabled

No AD user is currently selected

Temporarily disabled

The reset request is in progress, re-enables automatically on completion

Unavailable

A preview run is currently active, the control is hidden to prevent session state corruption during execution

When to use this

Use the session reset control when:

  • You want to verify the full authentication flow, including initial login, without cached cookies from a prior run carrying over.

  • An authentication failure has occurred and you want to rule out a stale or corrupted session as the cause.

  • You have updated the credentials or TOTP secret for an AD user and want to ensure the old session is no longer used.

  • A custom Auth Script is under development and you need each preview to start from an unauthenticated state.

What this does not affect

  • The reset clears the cached session cookie for the selected AD user on this sequence only.

  • It does not modify the user's credentials, TOTP secret, or any data item configuration.

  • It does not affect other AD users configured in the same or other sequences.