# How to reschedule or cancel a post from the DunSocial CLI

> Find the post id with dun posts list, then use reschedule to move it, cancel to stop a scheduled post, or delete --yes to remove it. Reschedule keeps the existing content, media & metadata unless you pass new --text.

Updated: 2026-10-05.

## Find the post first

Every change needs the post id. List posts, optionally filtered:

```bash
dun posts list
dun posts list --status scheduled --limit 20
dun posts list --account ACCOUNT_ID --json
```

Status values include `scheduled`, `published`, `failed`, `draft` & `cancelled`. JSON items include `mediaUrls`, which are the media asset ids.

## Look at one post

```bash
dun posts get POST_ID
```

Use it to confirm you have the right post before you change or cancel it.

## Reschedule

```bash
dun posts reschedule POST_ID --in 3h
dun posts reschedule POST_ID --at 2026-08-01T15:00:00Z --text "Updated copy"
```

If you omit `--text`, the CLI keeps the existing content, media & metadata. Pass `--text` only when you also want to change the copy.

## Cancel a scheduled post

```bash
dun posts cancel POST_ID
```

Cancel stops a post that hasn't gone out. It stays in your history with a cancelled status rather than disappearing, which is useful for an audit trail.

DunSocial keeps the cancelled post in history, so the calendar still shows what was planned.

## Delete

```bash
dun posts delete POST_ID --yes
```

Delete is destructive, so it needs `--yes` unless the `CI` environment variable is set. Prefer cancel when you might want a record of what was planned.

DunSocial's web app offers the same delete, if you'd rather do it there.

## In a pinch

If something should not go out at all, such as a post scheduled before bad news, list scheduled posts & cancel them in a loop. DunSocial's calendar shows the same posts, so a teammate can check the result without the terminal.

Pair the loop with `--json` so the script reads each id reliably instead of parsing text.

## Before a big batch

For X, check the monthly cap with `dun posts x-cap` before rescheduling many posts onto one day, since a cap hit will fail some of them.

DunSocial reports the cap as a rate-limit error, so a failed reschedule is easy to recognise.

## Related guides

- [How to schedule a post with the DunSocial CLI](https://www.dunsocial.com/hub/dunsocial-cli-guides/how-to-schedule-a-post-with-the-dunsocial-cli.md)
- [How to script the DunSocial CLI with JSON output](https://www.dunsocial.com/hub/dunsocial-cli-guides/how-to-script-the-dunsocial-cli-with-json-output.md)
- [What happens if a scheduled post fails?](https://www.dunsocial.com/hub/social-media-scheduler/what-happens-if-a-scheduled-post-fails.md)
- [Social media approval workflow](https://www.dunsocial.com/hub/social-media-management/social-media-approval-workflow.md)

## About this document

This is the Markdown representation of https://www.dunsocial.com/hub/dunsocial-cli-guides/how-to-reschedule-or-cancel-a-post-from-the-dunsocial-cli. The HTML version of the same page is at the same URL. You can also request Markdown from any page by sending `Accept: text/markdown`.

Machine-readable summary of the whole site: https://www.dunsocial.com/llms.txt

## Company

- Product: DunSocial, https://www.dunsocial.com
- Legal entity: THISUX PRIVATE LIMITED, Chennai, Tamil Nadu, India
- Support: support@dunsocial.com
- Open the app: https://app.dunsocial.com/login