source-tiktok-marketing: TikTok API returning code 50000 "System error." on /ad/get/ (2026-08-11)

[devin-ai-integration]

Summary

Since 2026-08-11 ~08:32 UTC, source-tiktok-marketing syncs have been failing with a TikTok-side generic internal error on /open_api/v1.3/ad/get/:

HTTP 200 {'code': 50000, 'message': 'System error.', 'request_id': '...', 'data': {}}

Sentry group: https://sentry.io/organizations/airbytehq/issues/7379973626/

Impact

16 Cloud connections across 15 workspaces. Failures hit both unpinned actors (Cloud GA 5.1.5) and rollout-pinned actors (5.1.8/5.1.9), so this is a TikTok-side issue, not a connector regression. Reproduction with Airbyte integration-test credentials returns code: 0 / OK, so the endpoint/param shape itself is fine.

Side effect on progressive rollouts

These TikTok failures tripped the AutoPilot failure threshold and auto-cancelled the 5.1.8 and 5.1.9 rollouts. Four affected actors remain pinned to 5.1.9 by cancelled rollout faf00bdb-3e5f-4219-9fce-75e716264681:

• 06b6f216-35fb-4e7c-9745-c65b4c72f62f (apex-dev)
• 6d172e68-1f67-4516-9c1d-331bde692559
• da077cb0-b13b-4cfc-96ce-c68ebb679583
• a993d5a6-8e87-4bd7-ad66-fea54a1034b9

Action

Unpin those four actors so they return to Cloud GA 5.1.5, and monitor whether the TikTok 50000 burst subsides on its own.

---

Internal Tracking: https://github.com/airbytehq/oncall/issues/13272

[octavia-bot]

AI Triage Starting...

Thank you for opening this issue! I'm an AI assistant that will do an initial review and may:

• Ask clarifying questions if needed
• Suggest relevant documentation or workarounds
• Flag this for internal visibility

Note: Community issues are reviewed on a best-effort basis and do not have a guaranteed response time. For additional help:

• Join the Airbyte Community Slack to connect with other users and community members
• If you're an Airbyte Cloud customer, you can open a support ticket or contact your account representative, referencing this issue URL

View playbook

• 🔗 Session URL: https://app.devin.ai/sessions/dd173066a41a4c18b5b005fa4d6e07ee

✅ Devin AI session created successfully!

[airbyte-support-bot]

Thanks for the detailed report!

We're already tracking this signature internally, so we've linked this report to the existing internal ticket rather than opening a new one. The engineering team is looking into it.

This issue is being tracked internally: https://github.com/airbytehq/oncall/issues/13272

If anyone else is seeing the same code: 50000 / "System error." responses on /open_api/v1.3/ad/get/, it's helpful to add the affected connector version and a redacted log excerpt in a fenced code block. Please make sure to mask or remove any sensitive information (API keys, access tokens, advertiser IDs, connection strings) before sharing logs.

---

Need more help? Join Airbyte Community Slack for peer support, or if you're a Cloud customer, open a support ticket referencing this URL.

[surajbirchwood]

Seeing this too. Self-hosted TikTok Marketing → Snowflake connection, ad/get failing since roughly 15 hours ago as of my end (started before ~2026-08-11 20:00 UTC based on my Airbyte dashboard, matches the reported ~08:32 UTC start).

Same signature: {'code': 50000, 'message': 'System error.'} on ad/get/?page_size=1000&advertiser_id=.... Confirming this is isolated to the ads stream specifically, every other stream on the same connection (ad_groups, campaigns, advertisers, advertiser_ids, all report streams) is syncing cleanly against the same advertiser_id and credentials. Upgraded the connector to the latest version and the error persists unchanged, consistent with this being TikTok-side rather than a connector regression.

request_id: 20260811232802EA659CDAA31110C7D35F

[koko3tallah]

Airbyte has now published a matching status incident for this exact code: 50000 signature:

https://status.airbyte.com/cmsq8ll0z00930znwi0jnaf27

The official page was posted at 15:21 UTC on August 12, marks TikTok Marketing Source as a partial outage, and is still investigating. That does not change the unpinning step in the issue, but it gives affected users one place to follow before treating repeated ad/get failures as a connector regression.

I normalized the acknowledgement and timestamps here as well: https://outagedeck.com/incidents/airbyte-tiktok-marketing-api-returned-a-transient-server-side-error-code-50000-2026-08-12?utm_source=github&utm_medium=issue_comment&utm_campaign=airbyte_tiktok_status&utm_content=timeline

I'm Kerolos, founder of OutageDeck. The Airbyte status page should remain the source of truth.