Scheduling
Post replies at the perfect time with automated scheduling
Overview
Scheduling allows you to compose replies now and have them automatically posted at a future time. This feature is integrated into Focus Mode for single replies and Reply Queue for bulk scheduling.
ThreadTrak uses Chrome Alarms and your X API credentials to post on your behalf, ensuring reliable delivery even when the X tab isn't open (Chrome must remain running).
Where to Find It
In Focus Mode
When composing a reply in Focus Mode, click the Schedule button next to the Send button. A date/time picker appears to set the exact posting time.
Focus Mode docsIn Reply Queue
Enter Select Mode, choose items with drafts, then click Bulk Schedule. Set a start time and step interval to schedule all selected items with smart staggering.
Reply Queue docsPrerequisites
X API Integration Required
Scheduling requires X API access because ThreadTrak needs to post on your behalf when you're not actively using the browser. The X API Free tier includes everything you need.
What You Need
- X Developer account (free)
- X API app with Read + Write permissions
- OAuth 1.0a credentials (4 keys)
- ThreadTrak Pro plan
Free Tier Limits
- 1,500 posts per month
- Resets monthly
- Counter shown in Scheduled Tweets panel
How Scheduling Works
The Scheduling Pipeline
User Interface
You pick a date/time in the Schedule Picker (Focus Mode or Queue Bulk)
Content Script
Captures your draft text and the target tweet's ID
Background Script
Stores the scheduled tweet in Chrome storage and creates a Chrome Alarm
Chrome Alarms
At the scheduled time (±1 minute), the alarm triggers the background script
X API
Background script uses your OAuth tokens to post the reply via X API
Works Without X Tab
You don't need to have X/Twitter open. The background script handles posting independently.
Chrome Must Be Running
Chrome needs to be open (not closed). Minimized or in background is fine.
Schedule Picker
Focus Mode (Single)
Date
Pick any future date from calendar
Time
Select hour and minute (24-hour format)
Click "Schedule" to confirm
Queue Bulk Schedule
Start Date/Time
When the first post should go out
Step Interval
1-60 minutes between each post
All selected items scheduled with staggering
The planScheduleTimes Algorithm
When bulk scheduling, ThreadTrak uses a smart algorithm to create natural-looking posting patterns:
Step Interval
1-60 min
Default: 15 min
Random Jitter
-2 to +3 min
For natural timing
Minimum Gap
2+ minutes
Always enforced
Conflict Avoidance
Smart
Skips busy times
Example: Scheduling 5 posts starting at 9:00 AM with 15-min step:
Post 1 → 9:00 AM + 2 min jitter = 9:02 AM
Post 2 → 9:15 AM - 1 min jitter = 9:14 AM
Post 3 → 9:30 AM + 3 min jitter = 9:33 AM
Post 4 → 9:45 AM + 0 min jitter = 9:45 AM
Post 5 → 10:00 AM - 2 min jitter = 9:58 AM
Scheduled Tweets Panel
Access from the Sidebar → Scheduled Tweets to view and manage all scheduled posts.
View Upcoming
See all pending posts sorted by scheduled time
Track Status
Monitor pending, posted, failed, and cancelled states
Cancel Posts
Cancel any pending post before it's sent
Status Lifecycle
Related Settings
Access via Sidebar → Settings:
scheduleTimeStepMinutes
Default step interval for bulk scheduling (1-60). Default: 15
bulkActionsEnabled
Enable/disable bulk scheduling in Queue
Twitter API Credentials
API Key, API Secret, Access Token, Access Secret
Troubleshooting
Scheduled post didn't send
Causes:
- • Chrome was fully closed (not just minimized)
- • X API tokens expired or revoked
- • Rate limit exceeded (1,500/month)
- • Network connectivity issue at execution time
Solution:
Check Chrome was running, verify API tokens in Settings, check remaining quota in Scheduled Tweets panel
"Not authenticated" error
Causes:
- • X API tokens not configured
- • Tokens expired and need refresh
- • App permissions changed on developer.x.com
Solution:
Go to Settings → Twitter, verify all 4 fields are filled, regenerate tokens if needed
Post failed with rate limit error
Causes:
- • Exceeded 1,500 posts/month on Free tier
- • Too many posts in short window (X side limit)
Solution:
Wait for monthly reset or upgrade X API tier, spread posts further apart
Schedule picker not appearing
Causes:
- • X API not connected
- • Not on Pro plan
- • Extension needs reload
Solution:
Verify Pro status and X API connection in Settings, reload extension if needed
Bulk schedule creating conflicts
Causes:
- • Step interval too small for number of posts
- • Many existing scheduled posts at similar times
Solution:
Increase step interval or choose different start time
Jitter causing posts too close together
Causes:
- • Random jitter pushed posts within 2-minute window
Solution:
This shouldn't happen—algorithm enforces 2-min minimum. If it does, report as bug
Known Limitations
| Limitation | Note |
|---|---|
| Chrome must be running | Background scripts require Chrome to be open (not necessarily focused) |
| 1,500 posts/month | X API Free tier limit—applies to all scheduled posts |
| No image attachments | Current version supports text-only replies |
| ±1 minute precision | Chrome Alarms has approximately 1-minute granularity |
| Single account | Scheduling is scoped to the currently logged-in X account |
Related Features
Pro Tips
- Schedule posts for your audience's peak times (usually 9am, 12pm, 6pm local time)
- Use 15-30 minute intervals for natural-looking engagement patterns
- Batch compose on weekends, schedule for weekday engagement
- Keep Chrome running (minimized is fine) to ensure posts go out
- Check Scheduled Tweets panel periodically for failed posts