vendor portal error questionnaire session timeout erased long narrative answers

TL;DR

Fix this in the vendor portal session handling by acting on the exact message first: draft long narrative answers in the answer library or a local document first, paste each finished answer into the portal, and save after every answer so a session timeout loses nothing already entered. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

vendor portal error questionnaire session timeout erased long narrative answers

Use this when

• The operation in the vendor portal session handling fails with this exact message: vendor portal error questionnaire session timeout erased long narrative answers.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the vendor portal session handling, and copy the full message plus the questionnaire, answer or evidence item involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: draft long narrative answers in the answer library or a local document first, paste each finished answer into the portal, and save after every answer so a session timeout loses nothing already entered. Verify: after a forced re-login every pasted answer is still present in the portal.
3. Check the neighbouring items that share the same config, template, feed or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions or alerts against the source in the vendor portal session handling so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in the vendor portal session handling on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

the portal session limit is shorter than the time needed to compose long answers in place, and unsaved answers lived only in the expired session.

Variant phrasings

vendor portal error questionnaire session timeout erased long narrative answers

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: vendor portal error questionnaire session timeout erased long narrative answers

The how-to phrasing for the same failure in the vendor portal session handling. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the vendor portal session handling troubleshooting for this failure

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

Compatibility: the vendor portal session handling at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

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