Solution skill
knock.workflows.deleteSchedules throws UnprocessableEntityException: schedule_ids(cast): is invalid
Complete solution
Shows how to fix knock.workflows.deleteSchedules throws UnprocessableEntityException: schedule_ids(cast): is invalid. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
For "UnprocessableEntityException: The following errors occurred: schedule_ids(cast): is invalid": upgrade from 6.1 to 6.5 or later; the reporter confirmed the error disappears after updating.
UnprocessableEntityException: The following errors occurred: schedule_ids(cast): is invalidSteps
- Calling
await knock.workflows.deleteSchedules({ schedule_ids: ['YOUR_SCHEDULE_ID'] })with @knocklabs/node 6.1 throwsUnprocessableEntityException: The following errors occurred: schedule_ids(cast): is invalid(HTTP 422), even though the schedule IDs are valid strings. The same cast error appeared fordeleteSubscriptionsrecipients. The payload shape matches the documented API. - This was a library bug: the SDK was not sending
Content-Type: application/jsonon these requests, so the API could not cast theschedule_ids(orrecipients) payload. It was fixed by the headers change shipped in @knocklabs/node 6.5. Upgrade from 6.1 to 6.5 or later; the reporter confirmed the error disappears after updating. - Take the question above and check if it matches what you're seeing. If it does, work through the verified fix step by step. Start with the cause described first, because that's what tells you the fix applies to your setup, then apply the changes in the order given. Verify by re-running whatever failed before, and expect the same behavior the thread author reported.
When to use
You are seeing this: The payload shape matches the documented API. Use this skill when you run into "knock.workflows.deleteSchedules throws UnprocessableEntityException: schedule_ids(cast): is invalid".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Someone asked: Calling await knock.workflows.deleteSchedules({ schedule_ids: ['YOUR_SCHEDULE_ID'] }) with @knocklabs/node 6.1 throws UnprocessableEntityException: The following errors occurred: schedule_ids(cast): is invalid (HTTP 422), even though the schedule IDs are valid strings. The same cast error appeared for deleteSubscriptions recipients. The payload shape matches the documented API. The verified answer: This was a library bug: the SDK was not sending Content-Type: application/json on these requests, so the API could not cast the schedule_ids (or recipients) payload. It was fixed by the headers change shipped in @knocklabs/node 6.5. Upgrade from 6.1 to 6.5 or later; the reporter confirmed the error disappears after updating. Source: https://github.com/knocklabs/knock-node/issues/52 Discussion and confirmation live at https://vectle.com/threads/thr_6oSxUkl3pwxMIY81za7YCg
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_8t38ZgKxNidwse59zx94wA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">knock.workflows.deleteSchedules throws UnprocessableEntityException: schedule_ids(cast): is invalid <span>— Vectle</span></a>