Not every unsuccessful survey has the same cause. You might not match the audience, the quota might be full, the responses might fail validation, or the session might encounter a technical error. Reading the result accurately helps you choose a useful next step instead of trying to fix a problem that is outside your control.

An audience screenout is a matching result

A researcher may need a particular age range, product owner, occupation, or household type. Screening questions determine whether you belong in that sample. If you do not, the survey can stop before the main questionnaire. That does not mean you answered badly, and changing the same answer next time just to qualify can create contradictions rather than a legitimate match.

A full quota is similar from your perspective but different operationally: you may fit the study, yet the required responses have already been collected. A study list can become stale while other users finish. Refreshing the wall later may surface new opportunities, but it does not reopen a closed research quota.

Quality rejection concerns the submitted responses

Quality validation can inspect attention checks, consistency, completeness, and the time or pattern of answers. Read each question and respond honestly, including open-text prompts. Do not invent demographic details or speed through a grid to chase the reward. A quality rejection may happen during the study or after later review, but the timing alone does not establish the cause.

A technical exit needs different evidence

  • Audience mismatch: keep the profile accurate and try a different available study.
  • Full quota: return to the wall and select another study without misrepresenting your profile.
  • Quality rejection: inspect your answering habits and preserve the exact result if you believe it is mistaken.
  • Technical exit: record the provider, study ID, device, error message, and point at which the session failed.

A failed redirect, unreadable page, or broken media task is not automatically a completed survey. Report the technical failure as such. Repeatedly refreshing, submitting again, or changing devices mid-attempt can make the record harder to interpret. Save the available evidence before restarting anything.

What happens to the points?

Do not expect the full listed reward from every unsuccessful attempt. FreeRBX's CPX screenout handling currently assigns 5 points when the applicable screenout notification is received, but that does not guarantee every exit generates that event. Other provider rules can differ. Use the actual credited activity, not a presumed consolation amount, when measuring progress.

If the result is unclear, quote the exact message in a support ticket and distinguish the expected listed reward from the points actually credited. A report with the study identifier and final status is more actionable than treating all screenouts, cancellations, and errors as the same missing-credit issue.