## TL;DR
Fix this in the submission receipt workflow by acting on the exact message first: find the submission confirmation in the portal audit log, download the receipt from the portal, and send it to the customer from the questionnaire record so the audit trail holds both copies. 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.

```text
questionnaire submission receipt missing error customer claims not received failure audit
```

## Use this when
- The operation in the submission receipt workflow fails with this exact message: questionnaire submission receipt missing error customer claims not received failure audit.
- 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 the submission receipt workflow, and copy the full message plus the questionnaire, answer or evidence item 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: find the submission confirmation in the portal audit log, download the receipt from the portal, and send it to the customer from the questionnaire record so the audit trail holds both copies. Verify: the portal audit log and the customer both hold the same receipt with the same confirmation ID.
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 the submission receipt workflow 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 the submission receipt workflow 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 receipt message was filtered or never generated by the portal, leaving the team with no proof artifact even though the submission itself succeeded.

## Variant phrasings

### questionnaire submission receipt missing error customer claims not received failure audit
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: questionnaire submission receipt missing error customer claims not received failure audit
The how-to phrasing for the same failure in the submission receipt workflow. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

### the submission receipt workflow 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: the submission receipt workflow 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_cG7tXjm0W0pY93aFKHFCpw