questionnaire evidence attach error document link broken in portal failure

Not specified by the original author.

TL;DR

Fix this in the customer portal evidence view by acting on the exact message first: replace the expiring file-share link with the trust center permalink for the same document, set the document sharing scope to the customer room, and reopen the portal page as the customer role to test it. 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.

questionnaire evidence attach error document link broken in portal

Use this when

• The operation in the customer portal evidence view fails with this exact message: questionnaire evidence attach error document link broken in portal.
• 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 customer portal evidence view, 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: replace the expiring file-share link with the trust center permalink for the same document, set the document sharing scope to the customer room, and reopen the portal page as the customer role to test it. Verify: the link opens the document while signed in with the customer-room role.
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 customer portal evidence view 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 customer portal evidence view 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 original link was a time-limited share created under an internal account, so it expired and was never visible to external portal users.

Variant phrasings

questionnaire evidence attach error document link broken in portal

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: questionnaire evidence attach error document link broken in portal failure

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

the customer portal evidence view 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 customer portal evidence view 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/pstcy7dARd8aPHEdKHiuUf3Q

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

Thread query: questionnaire evidence attach error document link broken in portal failure

TL;DR: Fix this in the customer portal evidence view by acting on the exact message first: replace the expiring file-share link with the trust center permalink for the same document, set the document sharing scope to the customer room, and reopen the portal page as the customer role to test it. 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.

Not specified by the original author.

TL;DR

Fix this in the SafeBase document request flow by acting on the exact message first: in SafeBase open the looping document request, replace the evidence link with the trust center permalink for the document, confirm the document sharing scope includes the requester room, and resend the request link. 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.

SafeBase error document request loops questionnaire evidence link never resolves

Use this when

• The operation in the SafeBase document request flow fails with this exact message: SafeBase error document request loops questionnaire evidence link never resolves.
• 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 SafeBase document request flow, 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: in SafeBase open the looping document request, replace the evidence link with the trust center permalink for the document, confirm the document sharing scope includes the requester room, and resend the request link. Verify: the requester opens the evidence document from the new link in one click with no loop back to the request page.
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 SafeBase document request flow 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 SafeBase document request flow 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 request pointed at a short lived share link that redirected back to the request page once it expired, so the requester circled without ever reaching the file.

Variant phrasings

SafeBase error document request loops questionnaire evidence link never resolves

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: SafeBase error document request loops questionnaire evidence link never resolves

The how-to phrasing for the same failure in the SafeBase document request flow. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the SafeBase document request flow 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 SafeBase document request flow 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_X8DeOr9xWRQr7pUSR4lVQA

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

Thread query: SafeBase error document request loops questionnaire evidence link never resolves

TL;DR: Fix this in the SafeBase document request flow by acting on the exact message first: in SafeBase open the looping document request, replace the evidence link with the trust center permalink for the document, confirm the document sharing scope includes the requester room, and resend the request link. 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.

Not specified by the original author.

TL;DR

Fix this in the questionnaire export by acting on the exact message first: shorten each truncated answer to fit the portal field limit shown on the portal form, move the overflow detail into an attached evidence document referenced from the answer, and re-export. 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.

questionnaire export error answers truncated in customer portal

Use this when

• The operation in the questionnaire export fails with this exact message: questionnaire export error answers truncated in customer portal.
• 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 questionnaire export, 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: shorten each truncated answer to fit the portal field limit shown on the portal form, move the overflow detail into an attached evidence document referenced from the answer, and re-export. Verify: the portal shows the full answer text for the previously truncated fields with the evidence reference visible.
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 questionnaire export 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 questionnaire export 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

portal answer fields cap length below the library answer length, and the export silently cut the text at the cap instead of flagging it.

Variant phrasings

questionnaire export error answers truncated in customer portal

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: how to fix questionnaire export error answers truncated in customer portal fails

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

the questionnaire export 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 questionnaire export 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_OwbKG0fS2KcBfiGu0VshEA

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

Thread query: how to fix questionnaire export error answers truncated in customer portal fails

TL;DR: Fix this in the questionnaire export by acting on the exact message first: shorten each truncated answer to fit the portal field limit shown on the portal form, move the overflow detail into an attached evidence document referenced from the answer, and re-export. 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.