TikTok Backstage Automation: connect sessions and maintain reporting imports

Owner access and credential preparation

All Backstage credentials and session controls are restricted to the main account owner. A sub-user sees Owner access required instead of these workspaces. Creator Data also requires access to the Agency / Team / Creator Monthly Leaderboard module.

Use the email and password for the intended TikTok LIVE Backstage account. The first setup requires a password. When updating an existing account, leaving the password blank retains the saved password. The page explicitly states that the password is stored as retrievable plain text in the application database; treat database and server access accordingly.

Save and test login queues a connection test. The worker tries the saved browser session first, then signs in again if the session is unavailable or expired. Connected means it detected the Backstage Workspace and retained browser session state, not that every export has already run.

Login & Session: read and maintain the connection

Connection shows Status, Saved session, Last attempt and Last success. A queued or running login disables another Test login again until the current attempt finishes. Use Test login again when credentials or session state need rechecking.

Session recheck pending means the saved connection is paused. The worker reopens its saved browser session every 30 minutes without submitting the password again, and resumes reporting once it confirms Workspace. The page shows when the next check becomes eligible. Failed passive checks retain the saved session; incorrect credentials are not retried automatically.

Temporary security screens can clear during a later session check. If TikTok keeps requiring a CAPTCHA, verification code or QR approval, that verification still needs to be completed. The page does not provide an interactive verification-code form, and automatic checks do not bypass TikTok’s security requirements.

Remove details removes saved Backstage credentials and browser session after confirmation. Developer mode is an advanced diagnostic option managed centrally in Account Settings with its configured password. It can expose worker traces and a protected latest security-step screenshot to the owner; it does not turn the screenshot into an interactive login form. Disable developer mode after diagnosis.

Daily Network Metrics: understand freshness and history

With a connected saved session, the collector checks approximately every five minutes. The cards show Diamonds today, Valid go LIVE rate and Active creators today. Diamonds may show both the original display string and a normalized number.

Metric date is based on Europe/London. Last checked and Last successful check are labeled UTC. Use the countdown, status badge and latest error together: a recent failed attempt does not mean the latest stored total is current.

Daily history shows date, Diamonds, Valid LIVE, Active and status. Owners can remove an eligible failed-date record using Remove; this is not an edit action for a successful capture. Add a missing daily total allows a whole non-negative Diamond total for a missing past date in the current London calendar month. It cannot replace an existing capture, fill a future date or backfill any arbitrary historic month.

Rookie Graduation: download, import and Discord stages

This workflow requests the evaluated-creators workbook from Backstage Business essentials, keeps a protected local copy and imports it into the Rookie Graduation leaderboard. The normal daily run is queued at 17:00 Europe/London when valid credentials and a connected saved session exist. Failed downloads may retry up to twice at 15-minute intervals.

Rookie Graduation and Creator Data recover automatically when a late Backstage preview or guide covers an export control. The worker retries the blocked step within the same run and can use the Notification panel if the fresh completion notice disappears. It still requires a new export confirmation and the matching workbook. Login and security verification can still require attention.

Before exporting, the worker checks that TikTok has selected the current UTC month and that Last update meets the freshness rule displayed on this account’s page. The usual rule is yesterday in UTC; accounts with a permitted delay can show a different allowed age. For the initial setup, when the network has no previous successful automated Rookie Graduation download or import, a Last update date mismatch is allowed and the actual data date is retained. Later exports are blocked if the date is stale.

If TikTok refreshes the workbook after the Last update check, the import accepts a newer data date only up to the previous UTC day of the saved download time. Every creator row must have the same valid data date. A successful import records that verified workbook date; stale, future or mixed-date workbooks still fail validation. Retrying later does not extend the accepted date window.

Download and import latest file starts the workflow when eligible. One successful download/import is allowed per UTC day, resetting at 00:00 UTC. A valid import becomes the authoritative monthly snapshot and sends the configured leaderboard summary once. Latest request separates Download, Leaderboard and Discord so you can distinguish a successful download from a failed import or delivery.

Latest downloaded file gives the stored workbook information and available download action. Workbook preview helps confirm the file content. Export history shows prior requests and results; use these before retrying a task you think was lost.

Creator Data: run after Rookie Graduation

Creator Data waits until that day’s Rookie Graduation pipeline reaches its final state, including the export, leaderboard import and Discord handoff stages. Waiting for Rookie Graduation explains why its start button may be unavailable.

The export selects all creators in Backstage and obtains the matching Creator data UTC+0 workbook covering the current UTC month through export time. The stored workbook then refreshes the Agency / Team / Creator Monthly Leaderboard snapshot. It is not an additive import of another month’s earnings.

Read its Latest request, Latest downloaded file, Workbook preview and Export history just as you do for Rookie Graduation. Download, import and Discord delivery have separate statuses. The one-success-per-UTC-day limit applies to this workflow as well.

Creator absence is checked only after a validated full automatic Creator Data import succeeds. A still-missing creator is marked as left and hidden from the creator directory after more than 48 accumulated healthy hours. Only intervals between consecutive successful daily download/import cycles count. Failed or retried downloads/imports, login failures and missed daily runs pause the clock; the first recovery import resumes from a new baseline without charging the outage. Manual uploads and partial Rookie reports do not advance this timer. Records and past performance are preserved.

Retry an import or deliberately replace a run

Retry import from stored file is available for an eligible failed import with a stored workbook. It reuses the existing file rather than asking TikTok for another successful daily download. Resolve the underlying error before retrying.

Cancel and queue fresh run or Reset and queue fresh run opens a confirmation. It retires current queued/running work, clears the day’s allowance and queues a fresh run when the saved session is connected. Existing workbooks, leaderboard data, export history and Discord delivery records are retained.

A replacement import with changed data can update the monthly totals and send another summary. A Discord message already in transit may still arrive and cannot be recalled. Use reset when you intend to replace a run, not simply because a slow stage is still working.

Frequently asked questions