A high-scoring submission is in my queue

The score is only the first step. After scoring, a few safety checks can route a submission to you even when the number looks fine, so the engine never auto-approves something that deserves a human look:

Author does not clearly match this advocate, and there is no known handle for them on that platform (status: author mismatch).
A social post never mentions your product or company (status: product mention missing). A social post cannot auto-verify without a mention.
The link and the screenshot disagree on the author, rating, or text (status: conflict detected).
The page was blocked or private so the engine could not read it (status: check this).

The specific reason is always shown on the submission. Open it, check the source with the Open to verify link, and approve or reject.

A reward has not gone out

Check three things, in order:

Release policy. If the workspace is on Hold for human approval, an AI verification does not pay out on its own. The verified reward waits in Rewards → Activity until a person releases it.
Delivery type. If the reward is Manual by team, someone on your team has to complete the delivery after it is released.
No reward on the campaign. If there is no reward attached, a verified submission is simply done, because there is nothing to send.

See How rewards work with verification for the full flow.

The review is not live yet

Some platforms moderate a review before publishing it, so a valid link can return “not found” for a while. The engine does not reject these on age alone. It marks the submission Not yet live and re-checks it over the next several days, escalating the wording as it ages:

Not yet live → Not yet live, stale → Likely not published.

It is only rejected if the platform says the content was removed or rejected, the link is clearly invalid, a screenshot contradicts it, or you reject it by hand. A submission at Likely not published is a good candidate for a manual decision.

”This link is already claimed”

The engine checks for duplicate proof before it scores anything:

The same advocate submitting the same link again is rejected as a duplicate, showing the existing status.
A different advocate submitting a link that is already verified or in review is rejected as URL already claimed.
A different advocate submitting a link that was previously rejected is allowed through, but flagged for your review.

This runs at submission time, so an advocate is told right away if their link is already in the system.

The content was deleted right after submitting

This is exactly what the cooldown is for. Verification does not start until a short waiting period (a 2-day cooldown by default) passes, and no reward can go out during it. Content posted just to grab a reward and then deleted is never verified and never rewarded, because it is no longer live when the engine checks.

GetApp and Software Advice submissions

These two platforms do not expose the actual review URL, so there is no link for the engine to read. Submissions for them are scored from the screenshot only, on a shorter rubric (author, rating, and date). Make sure the advocate’s screenshot clearly shows the reviewer name, the rating, and the date, or the submission will come to you for review.

I want to decide before the engine finishes

You can. Open the submission and use Approve & Reward or Reject; your verdict is set by hand and recorded against you in the history. If you would rather let the engine try again instead, use Re-run AI verification.

I turned AI verification off

Workspace off: the engine never runs, and every submission in every campaign goes to manual review. The per-campaign control is locked off.
Campaign off (workspace on): only that campaign’s submissions skip the engine and go to manual review.

In manual mode, submissions arrive in Need action with no AI score (shown as N/A), and you review the proof and decide. Manual decisions land in the same Verified and Rejected tabs as AI ones.

The score or verdict looks wrong

You are always in control. Open the submission, check the source with the View on link, and approve or reject it yourself. Your decision overrides the engine, and it is recorded with your email in the submission’s history. If the proof has changed since it was scored (for example a review that has since published), use Re-run AI verification to score it again.