aikido scan stuck in pending state, results never appear error

Not specified by the original author.

TL;DR

Fix this by acting on the exact problem first: in OneTrust, open the stuck assessment, check the assigned reviewer in the current workflow stage, reassign it from the inactive or unassigned reviewer to the active vendor risk approver group, add a review due date, and resend the review task so the stage moves from pending review to in review. Do not rerun the same operation unchanged, because the same inputs produce the same failure. Prove the fix on one assessment questionnaire first, then rerun the full scope and reconcile the results.

OneTrust vendor risk error assessment questionnaire stuck in pending review

Use this when

• The operation in OneTrust fails with this exact problem: OneTrust vendor risk error assessment questionnaire stuck in pending review.
• The same failure repeats on retry with unchanged inputs.
• A vendor risk review, questionnaire, screening or vendor record update 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 a risk judgement or a tier decision. That is a risk owner decision, not this failure.

Steps

1. Reproduce the failure on one named assessment questionnaire in OneTrust and record the full problem text plus the vendor, record or report 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 OneTrust, open the stuck assessment, check the assigned reviewer in the current workflow stage, reassign it from the inactive or unassigned reviewer to the active vendor risk approver group, add a review due date, and resend the review task so the stage moves from pending review to in review. Verify: the single failing assessment questionnaire now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring vendor records, questionnaires or reports that share the same workflow, template or schedule, because this class of failure rarely affects only one vendor. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in OneTrust 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 vendor supplied document, the questionnaire response or the risk 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 vendor record or review log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

OneTrust vendor risk error assessment questionnaire stuck in pending review

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

How to fix - OneTrust vendor risk error assessment questionnaire stuck in pending review

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

OneTrust 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

OneTrust holds an assessment in pending review when the review task is assigned but not actionable, either because the reviewer is inactive or unassigned or because a required response failed validation on submit, so the workflow never advances even though the questionnaire looks complete in the list view.

Edge cases

• The vendor record, questionnaire version or portal page changed after the failing run started. Refresh the current state and reapply the fix against the current values, not the values from the failed run.
• The single scope proof passes but the full rerun still fails on other vendors. Treat each remaining failure as its own scope, because a shared workflow, template or schedule can hide more than one cause.
• The source systems disagree on the correct value. The vendor supplied document governs what the vendor attested, the risk tool record governs the stored score or status, and the procurement record governs vendor identity and lifecycle status; record which source won and why.

Compatibility: OneTrust at current versions, plus the vendor risk, procurement or source system 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/pst_mF5XcwqJb44jRCzie9cnIg

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

Thread query: OneTrust vendor risk error assessment questionnaire stuck in pending review

TL;DR: Fix this by acting on the exact problem first: in OneTrust, open the stuck assessment, check the assigned reviewer in the current workflow stage, reassign it from the inactive or unassigned reviewer to the active vendor risk approver group, add a review due date, and resend the review task so the stage moves from pending review to in review. Do not rerun the same operation unchanged, because the same inputs produce the same failure. Prove the fix on one assessment questionnaire first, then rerun the full scope and reconcile the results.

Not specified by the original author.

TL;DR

The agent needs a watchdog, not patience. Give every scan a hard per-stage timeout, require progress evidence (new ports, new hosts, new lines in the output file) at least every few minutes, and define a fallback per stage: shrink, chunk, or skip. A scan with no progress for 10 minutes is a failed scan, not a running one.

pentest agent stuck on waiting for scan with no progress on authorized target

Use this when

• The agent shows no new output, no new findings, and no plan change for many minutes while a scan runs.
• The scan tool itself offers no progress bar the agent can read.
• The run has no per-stage timeout, so the agent waits forever.

Not for this skill when

• The scan is slow but the output file keeps growing. That is a pacing problem, not a hang.
• The target is genuinely unreachable and the tool errors out quickly. That fails fast already.
• A human tester explicitly asked the agent to wait for a long scan to finish. That is an instruction, not a breakdown.

Steps

1. Wrap every scan invocation with an explicit timeout, for example timeout 1800 nmap -p- TARGET_HOST -oA full_scan. Verify: a hung scan exits with code 124 instead of hanging the agent.
2. Require a progress check every 5 minutes: has the output file grown, or have new findings appeared since the last check. Verify: the agent logs one progress line per interval.
3. Define the fallback before the scan starts: if no progress in 10 minutes, first retry with a narrower scope (top 1000 ports instead of all ports), then chunk, then skip and record the gap. Verify: the fallback chain is written in the run plan, not improvised.
4. Split long scans into stages (discovery, port scan, service scan), each with its own timeout and checkpoint file. Verify: each stage writes its own output file before the next begins.
5. After the run, record skipped scans and their reason in the engagement notes so the human tester can decide whether manual follow-up is needed. Verify: the notes list every scan that did not complete.

Variant phrasings

agent waiting forever for scan to finish

Same watchdog pattern, symptom phrasing.

scan hang with no output in agent run

Tool-agnostic variant.

pentest agent frozen during long scan

Engagement-level phrasing.

Compatibility: GNU timeout on Linux/macOS scanning workstations. The progress-check pattern is harness-agnostic.

Why it happens

Agents inherit the shell's default behavior: wait until the child process exits. Scanners can sit for hours on filtered hosts without emitting anything the agent can read, and most harnesses have no default step timeout. The watchdog makes "no progress" an observable, actionable event.

Edge cases / pitfalls

• Do not set the timeout so low that legitimate slow scans always trip it. Calibrate from one known-good scan of a similar target first.
• Killing a scan mid-write can corrupt its output file. Prefer output formats that flush incrementally, and treat partial files as suspect until validated.
• Skipping is a finding in itself: an unscanned target is a coverage gap the report must disclose, not a silent omission.

Provenance

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

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

Thread query: pentest agent stuck on waiting for scan with no progress on authorized target

TL;DR: The agent needs a watchdog, not patience. Give every scan a hard per-stage timeout, require progress evidence (new ports, new hosts, new lines in the output file) at least every few minutes, and define a fallback per stage: shrink, chunk, or skip. A scan with no progress for 10 minutes is a failed scan, not a running one.

Not specified by the original author.

TL;DR

Fix this in the vendor questionnaire submission by acting on the exact message first: check the upload scan status for the held file, if the scan is stuck remove and re-upload the file in a portal supported format, and submit only when every file scan reads complete. 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 questionnaire error file upload virus scan pending blocks final submission

Use this when

• The operation in the vendor questionnaire submission fails with this exact message: vendor questionnaire error file upload virus scan pending blocks final submission.
• 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 questionnaire submission, 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: check the upload scan status for the held file, if the scan is stuck remove and re-upload the file in a portal supported format, and submit only when every file scan reads complete. Verify: all files show scan complete and the final submission is accepted.
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 questionnaire submission 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 questionnaire submission 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 holds submission while any attachment scan is pending, and one file scan stalled without notifying the submitter.

Variant phrasings

vendor questionnaire error file upload virus scan pending blocks final submission

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 questionnaire error file upload virus scan pending blocks final submission

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

the vendor questionnaire submission 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 questionnaire submission 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/pstgVsLWtrqAHpUHi5XN1usg

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

Thread query: vendor questionnaire error file upload virus scan pending blocks final submission

TL;DR: Fix this in the vendor questionnaire submission by acting on the exact message first: check the upload scan status for the held file, if the scan is stuck remove and re-upload the file in a portal supported format, and submit only when every file scan reads complete. 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.