platform engineer

scheduler health api for reliable, time-sensitive publishing

Let an agent check scheduler health before creating time-sensitive work. Machine-readable status and simple signals let you gate workflows, route work, and reduce missed posts while keeping human approval in the loop.

Human decision before publishing
Evidence and exceptions stay attached
No generated testimonial or outcome claim

Start a review-first workflow Verify current plans

Page-specific working plan

Scheduler Health API workflow checklist

A compact checklist to decide whether to create time-sensitive work, route to a fallback, or delay until health improves. Use these checks inside MCP agents or platform automation.

status == healthy

endpoint readiness check

Confirm the scheduler API returns a healthy state. If it reports degraded or unavailable, pause job creation and notify the operator.

median approval delay in seconds

approval-queue latency

Measure time to clear the single human approval queue. For time-sensitive posts, require that expected approval latency fits your publish window.

next-publish-times per account

publish window availability

Verify that the scheduler has available publish slots for each target account and platform, including Instagram, TikTok, and X.

retry count and fallback route

retry and fallback rules

If the scheduler is degraded, route drafts to a holding stream, escalate to a human, or schedule to an alternate publish window.

what it is

machine-readable scheduler health for operational decisions

The scheduler health api exposes a compact, machine-readable view of TTP scheduling state so agents and automation can decide whether to create time-sensitive work. Use its signals to gate job creation, choose a fallback path, or surface an alert to an operator.

This capability ties into platform facts you already rely on. Drafts remain in one human approval queue until approved, and approved posts publish at each account's best time. The health signals reflect the scheduler, the approval queue, and downstream posting to Instagram, TikTok, and X.

how to use it

check, decide, act: a simple agent flow

First, call the scheduler health api to get status, approval-queue latency, and next-publish windows for target accounts. If any signal is outside your service-level threshold, do not create time-sensitive work.

Next, take one of three actions. Create and route the draft to a holding stream for human review. Schedule the draft for the next available publish window. Or escalate to an operator for manual intervention. Agents on the MCP surface can run this flow without external API keys.

signals

key health fields and what they mean

The scheduler health api returns machine-readable fields you can use in logic. Typical fields include overall status, approval-queue latency, per-account next-publish-times, and recent publish error rates for Instagram, TikTok, and X.

Use these signals to make deterministic decisions. For example, require status == healthy and approval-queue latency below your threshold before creating any job labeled time-sensitive.

availability

permissions, approval, and plan limits you must know

The scheduler health api is accessible from inside a TTP workspace and via MCP agents. Because TTP keeps every draft in a single human approval queue, any scheduling decision that leads to publication still requires human approval before posting.

This feature is included on TTP's single plan. Enabling agent-driven checks requires workspace-level permission from an account owner or administrator. The API does not bypass the approval queue or publishing rules set by workspace administrators.

integration

integration patterns and recommended fallbacks

Use the scheduler health api as a gate for creating time-sensitive tasks. Pattern 1 is direct gating: block job creation if health signals fail. Pattern 2 is buffered scheduling: create drafts but route them to a holding stream until human approval and a healthy publish window.

For critical workflows consider a fallback to manual publish or alternate channels. Keep alerts simple and actionable so operators can clear the single approval queue when needed.

Questions for this workflow

Frequently asked questions

Is the scheduler health api included on my plan?

Yes. The scheduler health api is included on TTP's single plan. Access must be enabled by an account owner or administrator for your workspace.

Can an agent call the scheduler health api before scheduling time-sensitive work?

Yes. MCP agents can call the machine-readable scheduler health signals without external API keys. Agents should verify status, approval-queue latency, and next-publish-times before creating time-sensitive drafts.

Does the scheduler health api bypass human approval so posts can publish immediately?

No. TTP keeps every draft in one human approval queue until an authorized human approves. The scheduler health api provides signals to inform decisions, but it does not override approval or publishing rules.

What format and fields does the api return?

The api returns machine-readable JSON with fields such as overall status, approvalQueueLatency, nextPublishTimes per account, and recent publish errors by platform. Use these fields in agent logic to gate or route work.

Keep exploring

Best time to postTiming windows by platform.PricingCurrent plans and limits.MCP for agentsDrive the workflow from any MCP client.

Turn this plan into an approval-ready queue

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