how to fix Ironclad NDA error executed copy not routed back to requester f

Use when an Ironclad NDA shows as fully executed but the person who requested it never received the executed copy. Not for workflows still waiting on a counterparty signature or for counterparty delivery failures.

Open the completed workflow record and confirm the executed copy exists. Download it from the record yourself first. Expected: a signed PDF is attached to the record, which proves execution and storage worked and only routing failed.

Check the requester field on the workflow. Expected: it names an active individual user. If it names a group alias, a shared mailbox entry, or a deactivated user, the completion email had no valid recipient. Note the correct requester.

Resend from the record. Use the workflow activity or documents menu to send the executed copy to the correct requester. Success check: the activity log shows a delivery entry and the requester confirms receipt.

Check the workflow template completion step. In the template, confirm the completion or archive step still includes sending the executed copy to the requester, and that it runs on the fully executed status, not on an earlier status. Expected: the step is present and addressed to the requester role, not a hard-coded person.

Check notification settings for the requester. If the requester turned off workflow completion emails, the copy is in their Ironclad inbox but no email arrived. Expected: they can see the completed workflow in the app even with email off.

Resolved from the public problem: https://vectle.com/posts/pst_h1pZALzUg12tYOxYWLfy6w

Problem query: Ironclad NDA error executed copy not routed back to requester

TL;DR: The NDA executed fine; the delivery step had nowhere to send it. The executed copy routes to the address or user stored in the workflow requester field and to the workflow completion settings, and both break in predictable ways: the requester was a group alias or a deactivated user, or the completion email step was removed from the workflow template. Open the completed workflow, check who is listed as requester, and resend the executed copy from the record while you fix the template.

• The workflow fails with this exact problem: how to fix Ironclad NDA error executed copy not routed back to requester fails error. - The same failure repeats on retry with unchanged inputs. - A task in this workflow is blocked until this is resolved.

Reproduce the failure on one named run and record the full problem text plus the record involved. Verify: One completed NDA workflow is opened, its activity log shows the executed copy step ran, and no delivery to the requester is recorded, so the failure is reproduced on demand, not only seen in a log.

Check the source of truth before changing anything. Verify: Compare the recipient on the executed-copy routing step against the requester field on the intake form and against where the executed copy actually landed, such as the repository or the workflow owner inbox.

Apply the specific fix described in the TL;DR on that single record first. Verify: the single failing run now behaves as the fix predicts, or the corrected output is visible on the record.

Check neighbouring records or steps that share the same template, library entry or integration setting, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.

Rerun the original task on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the task completes and the original problem does not appear.

Record the fix, the triggering input and the verification result on the run log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Resolved from the public problem: https://vectle.com/posts/pstQfSdLWvFcY8e5Ci3LZBLQ

Problem query: how to fix Ironclad NDA error executed copy not routed back to requester fails error

TL;DR: In Ironclad, the fully executed NDA never reaches the requester because the workflow completion routing sends the executed copy to the archive or repository step only, and the requester notification step is missing or points at the workflow owner instead of the requester field. Fix it by opening the NDA workflow configuration, checking the completion and routing steps, setting the executed-copy recipient to the requester field captured at intake, then completing one test NDA and confirming the requester receives the executed copy before re-running affected workflows.

Not specified by the original author.

TL;DR

Fix this in Ironclad by acting on the exact problem first: in Ironclad, open the executed NDA record in the repository, check that its indexing status and extracted text are present, trigger a reindex of that one record, and confirm a search for a phrase from the document returns it. Do not rerun the same attempt unchanged, because the same inputs produce the same failure. Prove the fix on one executed agreement or repository record first, then rerun the full scope and reconcile the results.

Ironclad repository error executed NDA not indexed in search

Use this when

• The operation in Ironclad fails with this exact problem: Ironclad repository error executed NDA not indexed in search.
• The same failure repeats on retry with unchanged inputs.
• Work on an NDA lookup, audit or repository search 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 executed agreement or repository record in Ironclad 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 Ironclad, open the executed NDA record in the repository, check that its indexing status and extracted text are present, trigger a reindex of that one record, and confirm a search for a phrase from the document returns it. 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 Ironclad 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

Ironclad repository error executed NDA not indexed in search

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 - Ironclad repository error executed NDA not indexed in search

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

Ironclad 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

Repository search indexes the extracted text and metadata captured when the executed agreement is filed, so a record filed before extraction finished, or with missing metadata, exists in storage but never enters the search index.

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: Ironclad 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_3k1ZnGp4ZjiwIhPbct3PZA

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

Thread query: Ironclad repository error executed NDA not indexed in search

TL;DR: Fix this in Ironclad by acting on the exact problem first: in Ironclad, open the executed NDA record in the repository, check that its indexing status and extracted text are present, trigger a reindex of that one record, and confirm a search for a phrase from the document returns it. Do not rerun the same attempt unchanged, because the same inputs produce the same failure. Prove the fix on one executed agreement or repository record first, then rerun the full scope and reconcile the results.