Static UX shell. No backend calls, integrations, agents, or side effects.

Northstar Utilities | Field API

Production API calls started failing after yesterday's deploy

A spike in 422 responses started after a schema migration. The agent found a changelog and two similar tickets, but the proposed Jira escalation and customer reply require approval.

Back to queue

Needs reviewP1High risk

Run identity

Identifiers that should be propagated across TanStack Start, FastAPI, workers, queues, workflows, and LangSmith.

ticket_id

TCK-1048

run_id

RUN-7781

trace_id

trace-demo-3f82

thread_id

thread-fieldapi-northstar-1048

request_id

req_01HXDEMO1048

tenant_id

tenant_northstar

Automation decision

High risk

Customer-visible side effects remain blocked until the approval request is reviewed.

Trace handoff

Future LangSmith links should be persisted with run IDs and exposed here.

LangSmith trace placeholder

Mock trace ID trace-demo-3f82 is displayed without linking to a real external workspace.

Run timeline

Mock LangGraph node state with latency, cost, confidence, and approval wait markers.

Ticket normalized

Complete

Tenant, customer, severity, product area, request_id, and idempotency scope were attached to the run packet.

Latency

212 ms

Cost

$0.000

Confidence

100%

Classified as deploy regression

Complete

Matched Field API, production, P1 severity, and likely schema compatibility risk.

Latency

1.4 s

Cost

$0.012

Confidence

88%

Retrieved evidence

Complete

Selected a runbook, deployment changelog, service status snapshot, and one similar resolved ticket.

Latency

2.8 s

Cost

$0.006

Confidence

84%

Risk and action plan

running

Preparing a customer update plus a Jira escalation draft. External side effects are blocked until approval.

Latency

running

Cost

$0.014

Confidence

82%

Human approval interrupt

waiting

A reviewer must approve or edit the draft because the evidence includes a stale runbook and a customer-visible reply.

Latency

wait

Cost

$0.000

Confidence

requires reviewer

Idempotent tool execution

queued

The Jira draft and customer reply will use stable idempotency keys after approval.

Latency

n/a

Cost

$0.000

Confidence

blocked