workflows

Hello, Gunjan.

If you've recently edited your survey logic and noticed some responses appear missing or incomplete, it is likely due to the way active survey sessions handle configuration changes.

Survey sessions store both the response data and the question configuration (logic) that existed at the moment the session began.

• No Re-evaluation: If you make edits to the survey logic while a session is still active or in progress, that session does not automatically update or re-evaluate the new logic.

• Mismatched Data: This results in responses where questions may be missing, unanswered, or displayed unexpectedly because the response session is using the old survey configuration, not the new one.

• Recorded Data is Static: Once a survey session is closed and recorded as a response, any subsequent survey edits will not affect that recorded data.

The process of a session becoming a viewable response also introduces a delay:

• Temporary Storage: Session data is first stored temporarily (in MongoDB).

• Recording & Processing: It is then recorded in Atlas, processed, and cached before it appears in the Data & Analysis tab.

• SLA: While typical ingestion is fast, the Service Level Agreement (SLA) for a session to fully become a recorded response is roughly 6 hours.

To prevent missing or unexpected data, it is strongly recommended to avoid editing your survey logic while responses are actively being collected or sessions are in progress.

If you have confirmed that you made edits during active data collection and are now trying to reconcile missing data, or if you are still seeing issues with how data is being recorded:

• Submit a ticket through your Customer Success Hub: This is the fastest and most secure way to get a personalized resolution.

➡️ https://support-portal.qualtrics.com/