Troubleshooting

This page covers the three failure modes we see most often during early access. If none of them match, use the Send troubleshoot button in the extension popup — the operator sees your note plus the full capture payload and can dig in.

Extension not firing

Symptom: you placed an order, but nothing shows up in the dashboard recent captures.

1. Open chrome://extensions and verify Get PO'd is enabled.
2. Confirm you're on a Crow confirmation URL (the extension only runs on the right page).
3. Click the extension icon → Inspect service worker and look at the console. Background-worker breadcrumbs print each lifecycle step.
4. If you closed the confirmation tab within ~1 second of it loading, the capture can miss — refresh the confirmation page to retry.

"Capture rejected" notification

Symptom: the extension fires, but the dashboard shows failed.

1. Click the extension icon → Inspect service worker and scroll to the last error.
2. If it's a corestore_unauthorized, your API key is bad — see API key setup.
3. If it's a pipeline_error, check the backend log — it logs each ingest with timing, and surfaces the coreSTORE response body on failures.

Wrong line items / missing items

Symptom: the draft PO is created, but the lines don't match what you ordered.

1. Open the extension popup on any Crow page.
2. Click Send troubleshoot, add a short description of what's wrong, submit.
3. The operator reviews the report on /admin/troubleshoot with the full ingest payload, and can correct the parser or the store config.