Scheduling & Calendar
Plan your content calendar and schedule posts across all connected platforms from one unified view.
How Scheduling Works
When you compose a post and choose "Schedule", you pick a date and time for publication. FireBreath creates a scheduled job that automatically publishes your post at the exact time you selected. Posts are published via the platform's API — no manual intervention needed.
Scheduled posts appear in both the Calendar view and the Review Queue. You can edit a scheduled post at any time before it is approved (locked).
Calendar Views
The Calendar page offers three views:
- Month view — See your entire month at a glance. Each day shows the number of scheduled posts with color-coded status indicators.
- Week view — A more detailed week-by-week breakdown showing post titles, platforms, and times.
- Day view — Hour-by-hour timeline for a single day, useful for planning posting cadence.
Scheduling a Post
From the Compose page:
- 1.Write your content and attach any media.
- 2.Select one or more accounts to publish to.
- 3.Click "Schedule" and pick your date and time.
- 4.Click "Schedule Post" to confirm.
The post is saved with a scheduled job. It will publish automatically at the selected time.
Rescheduling and Cancellation
To reschedule a post, open it from the Calendar or Dashboard and change the scheduled date/time. The old scheduled job is automatically cancelled and a new one is created.
To cancel a scheduled post, delete it or change its status to Draft. This removes the scheduled job and prevents publication.
Scheduling Infrastructure
FireBreath uses a reliable three-layer publishing system:
- 1.QStash (primary) — Per-post scheduled jobs via Upstash QStash, an HTTP-based job scheduler. Each post gets its own delivery job.
- 2.Vercel Cron (fallback) — A minute-by-minute cron job checks for any posts that should have published but were missed by QStash.
- 3.Local dev — During local development, an in-process interval checks for due posts every 60 seconds.
This triple-layer approach ensures posts are published on time even if one system experiences issues.