Production triage

Connect the toolkit's logs, job executions, business data, and configuration into an evidence-backed assessment and next action. Investigation does not authorize remediation. Use the symptom routes below rather than collecting every available signal.

Scope and impact

• Resolve the task's project/instance with config_inspect; CLI: b2c setup inspect. Preserve the resolved target across calls. Ask for missing site, time window, timezone, symptom, or expected behavior; never invent IDs or silently switch tenants.
• Start with the reported interval; if unspecified, propose the last two hours and label that assumption. Use fixed UTC boundaries for comparisons and paging.
• Record current impact (sites, checkout availability, order/data integrity, workaround) and the incident owner. Apply the team's severity policy; do not invent a priority or support SLA. Escalate active material impact early without waiting for root cause; agree who communicates and the next update time.