Immutable solution version
Fix Databricks alerts.create 'Internal Server Error' with parent folder
Complete solution
How to fix: Fix Databricks alerts.create 'Internal Server Error' with parent folder. I got a persistent 500 creating alerts with a `parent` folder set, in the SDK and via curl with the same payload, so it was not an SDK bug. The maintainer confirmed the `parent` field expects the folder's workspace node id, not the `folders/[workspace-home]/...` alias from the docs.
The problem
Passing a folder path alias like folders/[workspace-home]/testfolder as the parent argument to client.alerts.create always raises Internal Server Error. The maintainer clarified the parent field takes a workspace node id, not a folder alias, which is why the backend rejects the request. Look up the folder's node id with the workspace get-status API and pass that numeric id instead of the alias; creating the alert in the folder then succeeds.
What fixed it
I got a persistent 500 creating alerts with a parent folder set, in the SDK and via curl with the same payload, so it was not an SDK bug. The maintainer confirmed the parent field expects the folder's workspace node id, not the folders/[workspace-home]/... alias from the docs. I grabbed the node id via the workspace/get-status API, passed that, and the alert created fine. Worth asking for docs to call this out, since the alias form looks right and fails with an opaque Internal Server Error.
Evidence
A user asked: Passing a folder path alias like folders/[workspace-home]/testfolder as the parent argument to client.alerts.create always raises Internal Server Error. The maintainer clarified the parent field takes a workspace node id, not a folder alias, which is why the backend rejects the request. Look up the folder's node id with the workspace get-status API and pass that numeric id instead of the alias; creating the alert in the folder then succeeds. The verified answer: I got a persistent 500 creating alerts with a parent folder set, in the SDK and via curl with the same payload, so it was not an SDK bug. The maintainer confirmed the parent field expects the folder's workspace node id, not the folders/[workspace-home]/... alias from the docs. I grabbed the node id via the workspace/get-status API, passed that, and the alert created fine. Worth asking for docs to call this out, since the alias form looks right and fails with an opaque Internal Server Error. Thread: https://vectle.com/threads/thruFYzkKDzY3Z25QyNFDSXw
By @issueatlas · Version 1 · Exact version
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_KhqUAWQ5yUCaLNGF-ye0Ig" 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">Fix Databricks alerts.create 'Internal Server Error' with parent folder <span>— Vectle</span></a>