Skip to content
Polaris Express Docs

Read a sync-run detail page

When a sync run finishes — or fails — you open its detail page to understand what changed and what broke. This runbook walks through every panel on the sync-run detail page so you can read it fluently when a customer complaint or a Lago discrepancy lands on your desk.

Prerequisites

Section titled “Prerequisites”
  • You are signed in to the admin console.
  • You have the sync run’s numeric ID, or you can reach it from the sync runs list at /sync.
  • For retrying failed runs, you need the admin role. Other roles can read the page but cannot trigger retries.

Procedure

Section titled “Procedure”

  1. Open the sync run

    Navigate to /sync/<id>, or click a row in the sync runs list. If the ID is invalid or the run does not exist, the console redirects you back to /sync.

  2. Read the Summary tile

    The Summary section shows four fields:

    • ID — the numeric run ID, matching the URL.
    • Status — Completed, Failed, or Running. The icon mirrors the badge: a green check, a red alert, or a spinning loader.
    • Time started — when the run began.
    • Duration — elapsed time. For a still-running run, this reflects time-so-far.

  3. Read the Statistics tile

    The Statistics section rolls up counters across the run. It has two groups:

    • EV Card linking — counts of EV cards activated, deactivated, and unchanged during the run.
    • Charging sessions — count of charging sessions processed and the number of events created downstream.

    A value of 0 means the segment ran but had nothing to do — not that the segment was skipped. To confirm a segment actually executed, switch to its tab in Segment details.

  4. Inspect segment logs

    The Segment details section is a tab strip. Each tab corresponds to one segment of the sync pipeline:

    • Tag linking — reconciling EV cards between Polaris and SteVe.
    • Transaction sync — pulling charging sessions from SteVe.
    • Scheduling — adaptive cadence decisions.
    • Lago customers, Lago subscriptions, Lago plans, Lago invoices, Lago wallets, Lago billable metrics — Lago-side reconciliation, one tab per resource.
    • Local reconcile — Polaris-side cleanup and consistency checks.

    Click a tab to see the log lines for that segment. If the run is still in progress, the tab content updates live.

  5. Read the Errors panel, if present

    If the run produced errors, an Errors section appears below the segment tabs with a red accent. The raw error text is shown as preformatted output — copy it verbatim when escalating.

    If there is no Errors section, the run completed without recording a top-level error. Per-segment failures may still appear inside the segment tabs.

Verify

Section titled “Verify”
  • The Status badge matches the run’s actual outcome. A Running badge with a stale start time means the run is hung; cross-check against the sync runs list at /sync.
  • The counters in Statistics are consistent with what you expect from the time window. For example, a tag-linking run during quiet hours typically shows small activation/deactivation counts and a large unchanged count.
  • Segment tabs contain log lines for the segments you expect to have executed.

If something goes wrong

Section titled “If something goes wrong”
  • Page redirects to /sync. The ID in the URL is non-numeric or the run was deleted. Re-open from the sync runs list.
  • Retry button is missing on a failed run. You are not signed in as an admin. Ask an admin to retry, or sign in with the correct account.
  • Counters are all zero but the run is Completed. The run executed but had no work to do. Confirm by opening one or two segment tabs — if they contain log lines, the run is healthy.
  • Errors section contains a stack trace. Copy the full text. Match the first error line to a segment by opening each tab; the segment whose logs end abruptly is usually the culprit.

Audit and reversibility

Section titled “Audit and reversibility”

Reading a sync-run detail page is a read-only operation and is not destructive. No audit entry is written for viewing the page.

Retrying a failed run from this page (via the Retry button) does create a new sync run with its own ID — it does not modify the original run record. Use the new run’s detail page to track the retry’s outcome.

Section titled “Related”