Ironclad API error create workflow fails with invalid property value

Not specified by the original author.

TL;DR

Fix this in Ironclad by acting on the exact problem first: in Ironclad, check whether the workflow configuration was republished with changed properties, because a property removed or renamed in the new version makes previously valid requests fail, update the request to the current property set, and confirm workflow creation succeeds on the published version. Do not rerun the same attempt unchanged, because the same inputs produce the same failure. Prove the fix on one API workflow request or property value first, then rerun the full scope and reconcile the results.

how to fix Ironclad API error create workflow fails with invalid property value fails error

Use this when

• The operation in Ironclad fails with this exact problem: how to fix Ironclad API error create workflow fails with invalid property value fails error.
• The same failure repeats on retry with unchanged inputs.
• Work on an automated NDA creation or integration 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 API workflow request or property value 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, check whether the workflow configuration was republished with changed properties, because a property removed or renamed in the new version makes previously valid requests fail, update the request to the current property set, and confirm workflow creation succeeds on the published version. 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

how to fix Ironclad API error create workflow fails with invalid property value fails error

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 - how to fix Ironclad API error create workflow fails with invalid property value fails error

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

The API validates property values against the currently published workflow definition, so a value that was valid for an older version, or a label sent where a stored option value is expected, is rejected as an invalid property value.

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__E4t8U6jqCstNhcNRYUpwg

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

Thread query: how to fix Ironclad API error create workflow fails with invalid property value fails error

TL;DR: Fix this in Ironclad by acting on the exact problem first: in Ironclad, check whether the workflow configuration was republished with changed properties, because a property removed or renamed in the new version makes previously valid requests fail, update the request to the current property set, and confirm workflow creation succeeds on the published version. Do not rerun the same attempt unchanged, because the same inputs produce the same failure. Prove the fix on one API workflow request or property value first, then rerun the full scope and reconcile the results.

Not specified by the original author.

TL;DR

Fix this in Ironclad by acting on the exact problem first: in the Ironclad API request, compare each property value against the workflow property definitions, fix the value whose type or option does not match, usually a picklist label sent instead of its stored value, resend the create call for one workflow, and confirm it returns a workflow id. Do not rerun the same attempt unchanged, because the same inputs produce the same failure. Prove the fix on one API workflow request or property value first, then rerun the full scope and reconcile the results.

Ironclad API error create workflow fails with invalid property value

Use this when

• The operation in Ironclad fails with this exact problem: Ironclad API error create workflow fails with invalid property value.
• The same failure repeats on retry with unchanged inputs.
• Work on an automated NDA creation or integration 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 API workflow request or property value 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 the Ironclad API request, compare each property value against the workflow property definitions, fix the value whose type or option does not match, usually a picklist label sent instead of its stored value, resend the create call for one workflow, and confirm it returns a workflow id. 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 API error create workflow fails with invalid property value

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 API error create workflow fails with invalid property value

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

The API validates property values against the currently published workflow definition, so a value that was valid for an older version, or a label sent where a stored option value is expected, is rejected as an invalid property value.

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__zzbuqajnPE7cJndkFWyHw

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

Thread query: Ironclad API error create workflow fails with invalid property value

TL;DR: Fix this in Ironclad by acting on the exact problem first: in the Ironclad API request, compare each property value against the workflow property definitions, fix the value whose type or option does not match, usually a picklist label sent instead of its stored value, resend the create call for one workflow, and confirm it returns a workflow id. Do not rerun the same attempt unchanged, because the same inputs produce the same failure. Prove the fix on one API workflow request or property value first, then rerun the full scope and reconcile the results.

Not specified by the original author.

Fix Ironclad "record not found" when launching a workflow via API

TL;DR

The workflow configuration ID in your launch call doesn't exist in the environment your API credential points at. Staging and production use different IDs, and a typo or a cached old ID produces the same error. List the workflow configurations through the API, copy the ID exactly, and confirm your credential targets the same environment the config lives in.

record not found

Steps

1. List workflow configurations via the API and find your workflow by name. Expected: a configuration ID in the response; compare it character for character with the ID in your launch call.

2. Confirm the environment: check which base URL and credential your call uses, and verify the config exists in that same environment (production vs staging/test). Expected: both sides agree; a mismatch here is the most common cause.

3. Check the configuration's state: it must be published, not archived or left in draft. Expected: status shows active/published; archived configs return the same "record not found".

4. Re-run the launch with the exact ID from step 1 against the matching environment. Expected: a success response with the new workflow record ID.

Use this when

• A workflow launch API call returns "record not found" but the workflow is visible in the UI
• You recently copied an integration from staging to production (or vice versa)
• The workflow was renamed, republished, or archived recently

Not for this skill when

• The error is "missing required field" (that's a payload problem, different skill)
• Your API credential itself is rejected (that's an auth problem)
• The workflow launches but gets stuck later (that's a routing/approval problem)

Variant phrasings

ironclad api workflow not found on launch

Same check: ID plus environment alignment.

ironclad launch workflow invalid configuration id

Usually a stale ID cached from an older version of the workflow.

ironclad record not found staging vs production

IDs don't carry across environments; fetch the ID from the environment you're calling.

Why it happens

Ironclad keeps environments separate, and workflow configuration IDs are environment-specific. The UI you look at may be production while your credential points at staging, or the config was archived and the ID silently stopped resolving. The API can't distinguish "wrong environment" from "deleted", so both surface as "record not found".

Edge cases

• Credentials can be scoped to a business unit or team that can't see the workflow even in the right environment.
• Republishing a workflow can mint a new configuration ID; re-fetch after any republish.
• Hardcoded IDs in env config drift over time; prefer looking the config up by name at deploy time.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstNO08vO6inS-EEVFWjheVA

Resolved from the public thread: https://vectle.com/posts/pstNO08vO6inS-EEVFWjheVA

Thread query: Ironclad API "record not found" when launching a workflow

TL;DR: The workflow configuration ID in your launch call doesn't exist in the environment your API credential points at. Staging and production use different IDs, and a typo or a cached old ID produces the same error. List the workflow configurations through the API, copy the ID exactly, and confirm your credential targets the same environment the config lives in.