TikTok UPLOAD mode: privacy_level silently dropped, posts stuck in QUEUE forever

[diogoalves25]

Bug Report

Description

TikTok slideshow posts via the API using content_posting_method: UPLOAD with privacy_level: SELF_ONLY stopped delivering to TikTok inbox as of March 25, 2026. Posts are accepted by Postiz (return a postId) but remain stuck in QUEUE state indefinitely. Manual posting from the Postiz web UI also fails.

Two bugs identified by Postiz support bot:

1. Missing privacy_level in UPLOAD mode (root cause)

• File: libraries/nestjs-libraries/src/integrations/social/tiktok.provider.ts, lines 498-506
• privacy_level is only included in the request body for DIRECT_POST mode (line 473), but is completely omitted for UPLOAD mode
• TikTok recently tightened API validation and now rejects/silently fails requests without privacy_level

2. Infinite polling loop with no timeout

• File: libraries/nestjs-libraries/src/integrations/social/tiktok.provider.ts, lines 385-444
• After sending the request to TikTok, Postiz polls indefinitely for confirmation
• If TikTok responds with an unexpected status (e.g. due to the malformed request), Postiz has no timeout — post stays in QUEUE forever

Steps to Reproduce

1. Connect a TikTok account
2. Create a post via API with content_posting_method: UPLOAD and privacy_level: SELF_ONLY
3. Post is accepted (returns postId) but never delivers to TikTok inbox
4. Post remains in QUEUE state indefinitely
5. Switching to DIRECT_POST also fails (same QUEUE state)
6. Manual posting from Postiz web UI also fails

Expected Behavior

• privacy_level should be included in UPLOAD mode requests to TikTok
• Posts should either deliver to TikTok inbox or fail with a clear error
• Polling should have a timeout so posts don't get stuck in QUEUE forever

Environment

• Postiz Cloud (postiz.com)
• TikTok integration ID: cmmtgprj700exox0ydby1hp5a
• Content type: PNG slideshow images (not video)
• Worked perfectly for 7+ days, broke mid-day March 25, 2026

Code References (from Postiz support)

• tiktok.provider.ts lines 498-506: UPLOAD mode missing privacy_level
• tiktok.provider.ts lines 463-496: DIRECT_POST mode correctly includes privacy_level at line 473
• tiktok.provider.ts lines 385-444: infinite polling loop
• post.workflow.v1.0.1.ts lines 176-187: publishes success notification regardless of actual TikTok status

[swaraj017]

Hi, I'd like to work on this fix. The root cause is straightforward — privacy_level is omitted from the post_info body in the UPLOAD branch of buildTikokPostInfoBody, while it is correctly included in the DIRECT_POST branch. I'll add it to the UPLOAD path and submit a PR shortly.

[diogoalves25]

Whatever it was , it fixed itself the post are working no need to do anything. Thank youSent from my iPhoneOn Apr 23, 2026, at 4:17 PM, Swaraj Gaikwad ***@***.***> wrote:swaraj017 left a comment (gitroomhq/postiz-app#1338) Hi, I'd like to work on this fix. The root cause is straightforward — privacy_level is omitted from the post_info body in the UPLOAD branch of buildTikokPostInfoBody, while it is correctly included in the DIRECT_POST branch. I'll add it to the UPLOAD path and submit a PR shortly. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[swaraj017]

Thanks for the update! A few points worth noting:

The missing privacy_level in UPLOAD mode is still present in the codebase regardless of current behaviour
TikTok's API validation is inconsistent — it can start enforcing this again at any time for any user
PR #1460 is a small defensive fix that aligns UPLOAD mode with DIRECT_POST mode as intended
Happy to keep it open for maintainer review

[AdrienLeKing]

@nevo-david bumping this — same bug hitting our production right now on Postiz Cloud since 2026-05-15 ~10:13 UTC.
Symptoms match the original report exactly: TikTok UPLOAD mode + SELF_ONLY, posts accepted by Postiz API (return postId) but stuck in QUEUE indefinitely, no error surfaced. All other publishing across our integrations worked fine until 10:13 UTC then complete silence.
Empirical: 8 posts PUBLISHED across our integrations today before 10:13, zero published since (8h+ stuck QUEUE).
PR #1460 contains the 3-line fix and matches the root cause analysis (privacy_level dropped in UPLOAD branch of buildTikokPostInfoBody). Could you reopen and merge it? The contribution gate that closed the PR is blocking what looks like a clean, low-risk fix for a recurring user-impacting bug.
Thanks!

[github-actions]

This issue is stale because it has been open for 90 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 7 days since being marked as stale.