Ляшик Іван
12/08/2025, 7:23 AMFailed to connect to airbyte-workload-api-server-svc:8007 (Connection refused)
• No exit code found. exitCode.txt does not exist
In the logs it looks like the sync crashes in the middle of the process, and the source container does not manage to write the exitCode.txt file before termination.
The data size per sync is approximately:
• 3.7M records emitted (~379 MB total)
• 3 streams (around 1M, 1.58M and 1.126M records)
• The sync runs for ~4 minutes before failing.
❓ Questions for Support
Could you please help me understand the root cause and how to resolve this issue?
1. What could cause the Workload Heartbeat Error?
2. Specifically, why would the workload be unable to connect to airbyte-workload-api-server-svc:8007 (Connection refused)?
3. Why does the workload container fail to create exitCode.txt?
4. This seems to indicate the container crashes abruptly rather than exiting gracefully.
5. Could this problem be related to insufficient resources (RAM/CPU) on the workload container or the workload-api-server?
6. If so, what are the recommended resource requirements for handling large syncs (~4M records / ~400 MB)?
7. Are there any known issues in Airbyte where the Workload API Server loses connection during high-volume syncs?
8. What additional logs or metrics would you need from my environment to further diagnose the issue?
9. (pods logs, describe output, node metrics, etc.)
10. Do you have recommended approaches for optimizing large syncs?
11. For example:
◦ Increasing workload / heartbeat timeouts
◦ Tuning CPU/RAM for workloads or API server
◦ Splitting the sync into smaller batches
◦ Using the new Worker mode or other scaling strategiesAlan Chan
12/08/2025, 8:17 AMFrancisco Carneiro
12/19/2025, 11:36 AMSudip Shrestha
12/24/2025, 5:28 AMThiago
12/31/2025, 3:27 AMAbdulAzeez Adesanya
02/23/2026, 10:20 AMTaimoor Ali
02/27/2026, 9:22 AMverbotenj
02/27/2026, 5:22 PMHongbo Miao
03/25/2026, 8:33 AMairbyte/webapp:2.0.1 is missing in Docker Hub right now, it would be great to add the missing Docker image, thanks! ☺️
https://github.com/airbytehq/airbyte/issues/75448Safan Abdul
03/31/2026, 4:15 AMw0000ng2
04/01/2026, 7:01 AMRoss Karnes
04/09/2026, 7:35 PMVikrant
04/14/2026, 5:30 PMRobson Hermes
04/16/2026, 2:14 PM2026-04-16 13:29:31,353 [main] ^[[34mINFO^[[0;39m c.z.h.HikariDataSource(<init>):79 - config-pool - Starting...
You can see it's not INFO , it's ``^[[34mINFO^[[0;39m` . Seems to be hardcoded, if I didn't miss anything.
Thank you 🙂Lucas Rodrigues Dhein
04/16/2026, 3:09 PMLionel Morlot
04/21/2026, 10:27 AMGuillaume Miara
04/24/2026, 5:29 PMKevin Lefevre
04/30/2026, 6:11 PMissues have been arbitrarily closed by devin-ai-integration 😕
A few examples:
• https://github.com/airbytehq/airbyte/issues/12437
• https://github.com/airbytehq/airbyte/issues/64156
• https://github.com/airbytehq/airbyte/issues/11157
• https://github.com/airbytehq/airbyte/issues/27067
• https://github.com/airbytehq/airbyte/issues/14064
• https://github.com/airbytehq/airbyte/issues/44858
Please could you reopen and prioritize them ?
Notably for Helm Chart & Destination GCS connector which should have been considered a long time ago 🙏
Thank you 🙂Abhishek Batra
05/12/2026, 2:21 PMHebert Douglas
05/12/2026, 8:39 PMElie Bismuth
05/25/2026, 8:35 PMad_creatives stream returns image_hash and video_id for many creatives instead of full-resolution URLs. We currently post-process via a custom worker calling /adimages?hashes=[...] (200/batch) and /?ids=v1,v2,...&fields=picture,thumbnails (50/batch) after each sync.
Two questions :
1. Is there a built-in or planned source config to resolve these natively (e.g.resolve_creative_thumbnails: true) so the URL lands directly in the`ad_creatives`stream?
2. Any best-practice pattern in the Airbyte ecosystem for post-sync enrichment that hits the source API for derived fields?Aivars Muskars
05/28/2026, 12:17 PM{
"i18nKey": "errors.http.badGateway",
"i18nParams": {
"status": 502
},
"name": "HttpError",
"requestId": "b9H3Q3Pg6aZKn4LMM313xE",
"request": {
"url": "/api/v1/web_backend/config",
"method": "GET"
},
"status": 502,
"response": "<!DOCTYPE html>\n<html>\n<head>\n<title>Error</title>\n<style>\nhtml { color-scheme: light dark; }\nbody { width: 35em; margin: 0 auto;\nfont-family: Tahoma, Verdana, Arial, sans-serif; }\n</style>\n</head>\n<body>\n<h1>An error occurred.</h1>\n<p>Sorry, the page you are looking for is currently unavailable.<br/>\nPlease try again later.</p>\n<p>If you are the system administrator of this resource then you should check\nthe error log for details.</p>\n<p><em>Faithfully yours, nginx.</em></p>\n</body>\n</html>\n"
}Elie Bismuth
06/02/2026, 8:31 PMsource) for ad creatives so we can display hover-to-play previews, similar to how we already handle image creatives.
We're running into an issue with a large number of ads that are partnership/branded-content ads. In these cases, the video belongs to a Facebook Page that isn't administered by the connected account (for example, an influencer's Page).
What we've observed so far:
• We can retrieve video IDs from ad creatives.
• The`Videos`stream (Meta's`/act_X/advideos`) only returns videos in the ad account's*own uploaded video library*— it never includes the*Page-post videos*that the ads actually reference (we measured*0 overlap*between ad creative`video_id`s and the`videos`stream),even for an account that administers the owning Page.
• The ad creatives streams provide thumbnails, but not the original video URL.
• Direct Graph API requests to retrieve the video`source`fail due to permissions because the connected account doesn't manage the Page that owns the video (error #10).
We found we can resolve the source via a Page access token (Graph API on the video node, using a token from /me/accounts) — but only when the connected user administers the owning Page. So our real question is whether the connector can fetch the video source via page tokens / the page node, rather than only the ad-account /advideos library.
A few questions:
• Has anyone encountered this limitation when working with Facebook Marketing ads?
• Is there a stream, field, or connector configuration that exposes the playable video URL for these ads?
• Or is this simply a Meta API permission restriction, meaning the video source is inaccessible unless the connected account has admin access to the owning Page?
Any insights would be greatly appreciated. 🙏Dawid Nawrot
06/13/2026, 7:18 AMMaximum capacity currently reached, additional jobs will be queued until capacity is available
Appeared out of the blue at 8pm yesterdayDouglas Reis
07/06/2026, 6:28 PMgagandeep.s
07/09/2026, 10:42 AMDawid Nawrot
07/12/2026, 8:32 PMSwan Sauvegrain
07/13/2026, 8:28 AMLiew Tze Hao Timothy
07/16/2026, 2:06 AMElie Bismuth
07/17/2026, 3:34 PMinsights and ad_creatives streams, instead of the full schema.
• Capped the insights lookback window to 14 days (insights_lookback_window).
• Rolling start_date (we pull the last 12 months of history, not all-time).
Our question: given the above, what else can we do on the Airbyte side to make recurring syncs faster and more reliable on large accounts?
A few specific things we're wondering about:
• Any recommended settings for the Meta connector to reduce sync duration on high-volume accounts ?
• Any best practices to avoid Meta API timeouts / rate-limit stalls during long syncs?
• Would incremental sync tuning or a different sync mode help here?
• Cloud vs self-hosted: would running self-hosted Airbyte give us meaningfully better performance or more control for large accounts like this?
Thanks a lot 🙏