TikTok spam_risk_too_many_posts vs reached_active_user_cap

Both are 403 errors from TikTok Direct Post, and both are daily limits. spam_risk_too_many_posts means the daily post cap from the API is reached for the current user. reached_active_user_cap means the daily quota for active publishing users from your client is reached. Neither is fixed by retrying today; hold the finished Sume videos and publish them on a later day.

TikTok's definitions are from its Direct Post reference; Sume's batch facts from Bulk runs and Structured output, read 2026-10-01.

What is the difference between the two errors?

Why does a Sume queue make this more likely?

A Sume bulk queue accepts up to 100 items, so one request can produce a day's worth of videos at once. Generation has no TikTok-side cap, but publishing does. Producing 100 videos for one account does not mean you can post 100 that day.

What do I do with the videos that wait?

Keep them. A finished run keeps its generated media with a durable URL and metadata, and media.sume.com URLs do not expire, so the files are there tomorrow. Store each URL against your own record with the date you plan to post, then publish a number you know is under the cap. TikTok's text here gives no number for the cap, so measure what your own client reaches.

How do I avoid the client-wide cap?

reached_active_user_cap is about how many distinct users your client publishes for in a day, so spreading posts across more accounts can hit it sooner. Keep a per-day list of the users you have published for, and defer the rest.

Also avoid reposting near-identical files; see reused content and batches. For per-token pacing see the 6 per minute limit.