How can we help you?

Response, Campaign, Delivery, and Export Status Reference

Product: FeraSurvey Topic: Reference Versions: Applies to all documented versions Current

Interpret status badges across response and operational records.

Audience: Administrators, analysts, and support
Editorial status: Public
Product: FeraSurvey

Overview

Interpret status badges across response and operational records.

Key points

  • Responses are Draft or Submitted and may be suppressed or reopened administratively.
  • Campaign and invitation statuses are server-defined.
  • Webhook deliveries show status, attempts, HTTP response, and last attempt.
  • Export states include queued, processing, completed, failed, expired, and canceled.
  • Operational health maps to active, warning, or failed styling.

Recommended procedure

  1. Identify the relevant survey, link, response, job, or route context.
  2. Use the reference value exactly as defined.
  3. Confirm the deployed API uses the same enum or identifier.
  4. Update dependent documentation and tests when the value changes.

Troubleshooting

An unknown value appears

Display it safely, do not treat it as success, and update the reference.

A value has different meaning in production

Correct the article from the authoritative server contract.

Related documentation