Three things found while editing two LinkedIn drafts on 2026-09-17.
-
drafts update <id> -f new.txt rebuilds the platforms block and DROPS the media that was attached at create time. Expected: keep existing media_ids unless --media/--media-file is passed. Workaround: a second drafts update <id> --append-media --media-file <path>.
-
drafts update with text applies the X 280 weighted check even when the draft is LinkedIn-only (created with -p linkedin). Expected: read the platform from the draft, or from -p, before checking. Workaround: -p linkedin --no-length-check.
-
There is no way to unschedule. PATCH /v2/social-sets/<set>/drafts/<id> with {"publish_at": null} returns the draft to draft; a drafts unschedule <id> (or update --unschedule) would wrap it.
Three things found while editing two LinkedIn drafts on 2026-09-17.
drafts update <id> -f new.txtrebuilds the platforms block and DROPS the media that was attached at create time. Expected: keep existing media_ids unless --media/--media-file is passed. Workaround: a seconddrafts update <id> --append-media --media-file <path>.drafts updatewith text applies the X 280 weighted check even when the draft is LinkedIn-only (created with -p linkedin). Expected: read the platform from the draft, or from -p, before checking. Workaround:-p linkedin --no-length-check.There is no way to unschedule.
PATCH /v2/social-sets/<set>/drafts/<id>with{"publish_at": null}returns the draft todraft; adrafts unschedule <id>(orupdate --unschedule) would wrap it.