15Five engagement report error sentiment themes missing for open comments

TL;DR

Fix this in 15Five by acting on the exact problem first: in 15Five, open the engagement report for the survey, check whether open comments were included in the report scope, confirm sentiment analysis has finished processing for that survey, rerun the theme generation for the comment set, and check themes against twenty raw comments before sharing the report. Do not rerun the same survey, report or export unchanged, because the same inputs produce the same failure. Prove the fix on one survey, team or department first, then rerun the full scope and reconcile the results.

15Five engagement report error sentiment themes missing for open comments

Use this when

• The operation in 15Five fails with this exact problem: 15Five engagement report error sentiment themes missing for open comments.
• The same failure repeats on retry with unchanged inputs.
• A survey launch, results dashboard, manager report or action plan is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with an interpretation call such as which driver to prioritise. That is a people analytics judgement, not this failure.

Steps

1. Reproduce the failure on one named survey, team or department in 15Five and record the full problem text plus the survey, team or period involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: in 15Five, open the engagement report for the survey, check whether open comments were included in the report scope, confirm sentiment analysis has finished processing for that survey, rerun the theme generation for the comment set, and check themes against twenty raw comments before sharing the report. Verify: the single failing survey, team or department now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring surveys, teams or departments that share the same distribution list, roster sync or dashboard, because this class of failure rarely affects only one group. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in 15Five on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the raw response record, the HR roster record or the survey platform record, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the survey run log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

15Five engagement report error sentiment themes missing for open comments

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single group proof, then the full rerun.

How to fix - 15Five engagement report error sentiment themes missing for open comments

The how to phrasing for the same failure in 15Five. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

15Five troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

Sentiment themes in 15Five come from a processing step over included open comments, so comments excluded from the report scope, or a processing step still running, leaves the theme section empty while scores show normally.

Edge cases

• The survey was reopened, the roster was resynced or a team was restructured after the failing run started. Refresh the survey state and reapply the fix against the current values, not the values from the failed run.
• The single group proof passes but the full rerun still fails on other groups. Treat each remaining failure as its own scope, because a shared distribution list or dashboard can hide more than one cause.
• The source systems disagree on the correct value. The raw response record governs response counts, the HR roster governs who was invited, and the platform record governs what was sent or shown; record which source won and why.

Compatibility: 15Five at current versions, plus the survey platform, roster or reporting tool the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst7oKtie7c2PCtva8EIRKrQ