for operations engineers
Verify the background scheduler is healthy before you trust unattended queues. Use a concrete runbook and the TimeToPost workflow checks to reduce missed publishes and stale drafts.
what this is
Reduce publication risk by verifying the scheduler and approval flow before enabling unattended queues. TimeToPost holds every draft in one approval queue until a human approves, and the scheduler publishes at each account best time once approvals are released.
This page focuses on operational checks you can run quickly. It covers approval queue health, publish audits for Instagram, TikTok, and X, account connection checks, and where to confirm plan limits and agent activity.
quick checks
Run these checks at the start of each shift or before enabling unattended publishing. Each check maps to a concrete action in the TimeToPost dashboard or account settings.
If you find anomalies, pause unattended publishing until the root cause is addressed. Many issues trace to approvals, account connections, or plan limits rather than the scheduler itself.
runbook
Follow these steps before you rely on unattended queues. Execute them in order so you can escalate efficiently when an issue appears.
Document findings after each step. Use the notes to decide whether to continue with unattended posting, to throttle volume, or to pause the queue until resolved.
integrations and automation
If you need scheduled monitoring or automated alerts, use the MCP surface. Agents drive TimeToPost automation without API keys, so you can build an internal agent to check approval queue age, publish timestamps, and agent run status.
TimeToPost does not replace your incident system. Use agents to surface findings into your toolchain, or export logs and alerts into your existing monitoring and paging services.
decision guide
Trust unattended queues when backlog is under control, recent publishes match expected cadence, account connections are healthy, and no repeating errors appear in logs. Confirm plan limits will not throttle the expected volume.
Keep manual approval if you see stale drafts, repeated post failures, or agent run errors. Plan to re-run the monitoring checklist after fixes and before you re-enable unattended publishing.
Questions for this workflow
TimeToPost surfaces approvals, drafts, and publishes through the platform. It does not replace your incident system. For periodic checks and automated alerts, use the MCP surface. Agents drive TimeToPost automation without API keys, so you can build agent-driven status checks and push results into your monitoring tool.
Run the workflow checklist: confirm the approval queue has no stale items, audit recent publish timestamps for each connected account, review activity and error logs for failed posts, and verify account authentication. Also confirm your TimeToPost plan limits so posting volume will not be throttled.
TimeToPost provides activity and error records you can inspect. For automated alerts, use the MCP surface to build agents that check logs and push alerts to your incident system. This approach keeps approval and publishing controls within the platform while automating monitoring.
Yes. TimeToPost requires human approval from users with approval permission before publishing, and account or rate limits in your plan can affect posting throughput. Review your plan details in account settings or plan documentation before enabling large unattended campaigns.
Start with the workflow above, keep the human review gate, and adapt the cadence to the accounts you actually operate.
Start a review-first workflow