Overview
Scheduled publishing allows you to set a future publish date for articles. Skayle’s sync job automatically publishes content when the scheduled time arrives.How It Works
- Set a future publish date on your article
- Article enters the publishing queue
- Cron job runs every 5-15 minutes
- When publish time arrives, content syncs to CMS
Setting Up Scheduled Publishing
Step 1: Configure Publish Date
In the Skayle editor:- Open your article
- Click Settings in the sidebar
- Set Publish Date to your desired time
- Save the article
Step 2: Queue for Publishing
- Click Schedule instead of Publish
- Article status changes to “Scheduled”
- Article appears in the publishing queue
Step 3: Monitor Queue
View scheduled articles in Content → Scheduled:| Article | Scheduled For | Status |
|---|---|---|
| New Feature Announcement | Jan 20, 2024 9:00 AM | Queued |
| Product Update | Jan 22, 2024 10:00 AM | Queued |
Cron Job Configuration
The sync job runs on a configurable interval:| Setting | Default | Range | Description |
|---|---|---|---|
| Sync Interval | 5 min | 1-60 min | How often to check for scheduled content |
| Batch Size | 10 | 1-50 | Max articles per sync run |
| Retry Attempts | 3 | 1-10 | Retries on failure |
| Retry Delay | 60 sec | 30-300 sec | Delay between retries |
Configuring the Interval
- Go to Settings → Publishing
- Set Sync Interval (recommended: 5-15 minutes)
- Save settings
Shorter intervals mean faster publishing but more API calls. Balance based on your CMS rate limits.
Publishing States
Articles move through these states:| State | Description |
|---|---|
| Draft | Not scheduled, won’t sync |
| Scheduled | Queued for future publish |
| Publishing | Currently syncing to CMS |
| Published | Successfully synced |
| Failed | Sync failed, will retry |
Timezone Handling
Skayle converts times to UTC for storage and back to your timezone for display:- You schedule for “Jan 20, 9:00 AM EST”
- Stored as “Jan 20, 14:00 UTC”
- Displayed as “Jan 20, 9:00 AM EST”
Failure Handling
When publishing fails:- Article marked as “Failed”
- Error logged with details
- Automatic retry after delay
- After max retries, requires manual intervention
Common Failures
CMS API unavailable
CMS API unavailable
Rate limit exceeded
Rate limit exceeded
- Reduce batch size
- Increase sync interval
- Will auto-retry with backoff
Validation error
Validation error
- Check article content
- Verify required fields
- May need manual fix
Taxonomy not found
Taxonomy not found
- Run taxonomy sync first
- Check category/tag mappings
- May need manual fix
Notifications
Configure notifications for publishing events:| Event | Notification Options |
|---|---|
| Published | Email, Slack, Webhook |
| Failed | Email, Slack, Webhook |
| Retrying | Slack, Webhook |
Setting Up Notifications
- Go to Settings → Notifications
- Enable desired channels
- Configure webhook URLs or Slack integration
- Select events to notify
Best Practices
- Schedule with buffer: Schedule 15+ minutes in the future for reliability
- Check queue regularly: Monitor the scheduled queue for stuck items
- Test with drafts: Test your workflow with non-critical content first
- Set up notifications: Get alerted on failures immediately
- Sync taxonomies first: Ensure categories/tags exist before scheduling
Bulk Scheduling
Schedule multiple articles at once:- Select articles in Content view
- Click Bulk Actions → Schedule
- Set publish date/time
- Optionally stagger (e.g., 1 hour apart)
- Confirm scheduling