how to fix URL detonation enrichment error sandbox report not attached failure

TL;DR

Fix this in URL detonation enrichment by acting on the exact message first: change the enrichment step to poll the sandbox until the report reaches a completed state (with a bounded wait), then attach the report link and verdict to the incident, instead of reading the report once at submission time. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

URL detonation enrichment error sandbox report not attached

Use this when

• The operation in URL detonation enrichment fails with this exact message: URL detonation enrichment error sandbox report not attached.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in URL detonation enrichment, and copy the full message plus the alert, incident or enrichment record involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: change the enrichment step to poll the sandbox until the report reaches a completed state (with a bounded wait), then attach the report link and verdict to the incident, instead of reading the report once at submission time. Verify: the incident gains the completed sandbox report link for a test URL.
3. Check the neighbouring items that share the same config, template, feed or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions or alerts against the source in URL detonation enrichment so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in URL detonation enrichment on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

the step read the report while analysis was still running, got an empty result, and never went back for the finished report.

Variant phrasings

URL detonation enrichment error sandbox report not attached

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: how to fix URL detonation enrichment error sandbox report not attached failure

The how-to phrasing for the same failure in URL detonation enrichment. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

URL detonation enrichment troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: URL detonation enrichment at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_stTOh7WTDd-UPcxD74HEaA