> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/web-app-features/content-calendar/tutorial.md). # Tutorial Manage scheduled, published, and failed posts in the redesigned Calendar and Posts screens without duplicate submissions. To schedule a new draft, follow [Schedule Posts](/web-app-features/content-calendar/schedule-posts.md). Use this page for content already submitted. ## Navigate to Calendar Calendar displays 1 week at a time. There is no month-view switch in this screen. Weekly posting schedule below the calendar contains recurring timing rules, separate from posts already scheduled. 1. Open [Calendar](https://my.blotato.com/calendar) from either mode. 2. Use Previous week, Next week, or Today to choose a week. 3. Select a time block to inspect the posts inside. 4. Select Weekly schedule to jump to recurring slots. [Posts](https://my.blotato.com/posts) provides a separate list with All, Scheduled, Published, and Failed filters. The old Upcoming Posts, Published Posts, and Failed Posts navigation items are no longer the starting points. ![Posts screen with status filters and platform and time-window selectors](https://2374509648-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FevfU9S4Nh53PiGflQLah%2Fuploads%2Fgit-blob-8254f4c85eddb7d53975a6c86917b49222848ac5%2Fui-posts-filters-2026-09.jpg?alt=media) ## Managing Scheduled Posts ### Can I filter the calendar by brand, account, or page? Calendar does not expose a brand, account, or Page filter. To narrow the list by platform: 1. Open [Posts > Scheduled](https://my.blotato.com/posts?status=scheduled). 2. Select a platform. 3. Check the account shown on each post. Use the [Scheduled Posts API](/rest-api-reference/schedules.md) for account-specific lists in your own integration. Selecting a brand in Post editor does not filter Calendar. ### Edit Scheduled Post Select Move to drafts to change a scheduled post's content or media. The redesigned Posts list does not use the old inline text-editor instructions. ### Reschedule Scheduled Post 1. Open Posts > Scheduled. 2. Select Reschedule on the intended post. 3. Choose the new date and time. 4. Select Save. 5. Verify the updated time. Reschedule changes the time while keeping the post scheduled. ### Move Scheduled Post Back to Drafts 1. Open Posts > Scheduled. 2. Select Move to drafts on the intended post. 3. Read the confirmation. 4. Select Yes to remove the schedule and return the content to drafts. 5. Blotato opens the post in [Remix](https://my.blotato.com/remix) for editing. 6. Submit a new publishing or scheduling action after review. This action removes the existing schedule. Moving to drafts does not publish the post. ### Delete Scheduled Post Scheduled rows in the redesigned Posts screen have Reschedule and Move to drafts actions, not the old bulk-delete control. Use Move to drafts to cancel a future publication while retaining its content. For schedule deletion through an integration, follow the [Scheduled Posts API](/rest-api-reference/schedules.md). Do not delete a published platform post to cancel a future schedule. ## Viewing Published Posts 1. Open [Posts > Published](https://my.blotato.com/posts?status=published). 2. Select the platform if needed. 3. Choose Past 7 days, Past 30 days, or Past 90 days. 4. Open the destination post to verify publication. For rankings and engagement summaries, use [Analytics](/web-app-features/analytics.md), not an older Top Performing tab. ## Troubleshooting Posts that Failed to Publish 1. Open [Posts > Failed](https://my.blotato.com/posts?status=failed). 2. Select the relevant platform and time window. 3. Read the failed destination's error. 4. Follow the matching [error explanation](/support/errors.md). 5. Check whether another destination already published. 6. Select Move to drafts when you are ready to correct the content and retry through Remix. Reconnect only for a connection or permission error. For a media error, check the [media requirements](/rest-api-reference/publish-post/media.md). Delete on a failed row removes its failed-post record, not a post already published on the social platform. For activity details, switch to Developer Platform and open [Logs](https://my.blotato.com/logs). Filter by activity type, result, platform, or account. An empty filtered list does not prove the submission never existed. Check the other status filters and time windows before resubmitting. See [Find a post's outcome before retrying](/start-with-an-ai-agent/publishing-status.md). ## Manage Your Calendar via API Use [Schedule and manage posts](/agent-workflows/agent-workflows/schedule.md) for the external-assistant workflow. REST and MCP expose different operations. * [Scheduled Posts API](/rest-api-reference/schedules.md) * [Schedule Slots API](/rest-api-reference/schedule-slots.md) * [Calendar Management Recipes](/api-and-mcp-concepts/workflows.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.blotato.com/web-app-features/content-calendar/tutorial.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.