## TL;DR
Fix this in the NDA routing workflow by acting on the exact problem first: in the routing rules, compare the countersignature step owner against the current approver list for this agreement type, correct the rule that points at the wrong approver, reroute the waiting NDA, and confirm the countersignature request now sits with the intended approver. Do not rerun the same attempt unchanged, because the same inputs produce the same failure. Prove the fix on one routing rule or approver assignment first, then rerun the full scope and reconcile the results.

```text
NDA routing error countersignature sent to wrong internal approver
```

## Use this when
- The operation in the NDA routing workflow fails with this exact problem: NDA routing error countersignature sent to wrong internal approver.
- The same failure repeats on retry with unchanged inputs.
- Work on an NDA countersignature or internal approval 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 clause wording or a legal judgement. That is a legal owner decision, not this failure.

## Steps
1. Reproduce the failure using one routing rule or approver assignment in the NDA routing workflow and record the full problem text plus the record, signer or run 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 the routing rules, compare the countersignature step owner against the current approver list for this agreement type, correct the rule that points at the wrong approver, reroute the waiting NDA, and confirm the countersignature request now sits with the intended approver. Verify: the single failing scope now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring records, templates or runs that share the same settings, template or schedule, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in the NDA routing workflow 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 executed NDA, the counterparty record or the repository entry, 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 workflow log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

## Variant phrasings

### NDA routing error countersignature sent to wrong internal approver
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 - NDA routing error countersignature sent to wrong internal approver
The how to phrasing for the same failure in the NDA routing workflow. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

### NDA routing 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
Routing rules and saved request assignments can disagree, and when the saved assignment wins, the NDA goes to whoever was named when the request was created, even after the approver group changed.

## Edge cases
- The record, template or assignment 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 items. Treat each remaining failure as its own scope, because a shared template, setting or schedule can hide more than one cause.
- The source systems disagree on the correct value. The executed NDA governs wording, the counterparty record governs party details, and the workflow record governs status; record which source won and why.

Compatibility: the NDA routing workflow at current versions, plus the NDA template, repository or messaging 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/pst_42TNc2pRCPVrJrlD6IybTQ