Custom declarative source sync fails: "Failed to wait for exit value file /dest/exitCode.txt" - Both Cloud and Self-hosted

[dev-sankalp]

Helm Chart Version

2.0.19

What step the error happened?

During the Sync

Relevant information

Environment:

• Airbyte Version: 2.0.1 (Self-hosted on Azure Linux VM)
• Airbyte Cloud: Also tested
• OS: Ubuntu 24.04

Description:
Custom YAML connector built using Connector Builder fails to sync
to any destination. Tried both Airbyte Cloud and self-hosted 2.0.1.

What we tried:

1. Custom YAML declarative source with JSONPlaceholder API
2. Multiple destinations tested:
   • Azure Blob Storage
   • End-to-End Testing (dev/null)
3. Airbyte Cloud (build-24075 and build-24078)
4. Self-hosted Airbyte 2.0.1 on Azure Linux VM (16GB RAM)

Error:
Failed to wait for exit value file /dest/exitCode.txt
Killing orchestrator because of an Exception
Streams without a status message: [posts]

Expected Behavior:
Data should sync from custom declarative source to destination.

Actual Behavior:
0 records extracted, 0 records loaded. Orchestrator crashes.

Relevant log output

2026-02-20 22:51:27 platform INFO Writing output of 8b01f408-723f-4759-ad64-0715bdafbcaa_1771545600000_discover to the doc store
2026-02-20 22:51:27 platform INFO Marking workload 8b01f408-723f-4759-ad64-0715bdafbcaa_1771545600000_discover as successful
2026-02-20 22:51:27 platform INFO Deliberately exiting process with code 0.
2026-02-20 22:51:27 platform INFO 
2026-02-20 22:51:28 platform INFO APPLY Stage: BUILD — (workloadId=ad25cf65-7e45-4680-b89b-a2ba7c61b3a8_1_0_sync)
2026-02-20 22:51:29 platform INFO APPLY Stage: CLAIM — (workloadId=ad25cf65-7e45-4680-b89b-a2ba7c61b3a8_1_0_sync)
2026-02-20 22:51:29 platform INFO Claimed: true for workload ad25cf65-7e45-4680-b89b-a2ba7c61b3a8_1_0_sync via API in dataplane ea2eda3b-2f9b-4ca4-b990-3c8d551ea995 (f28f991b-a8b2-4926-b44d-3635bd48d18e)
2026-02-20 22:51:29 platform INFO APPLY Stage: LOAD_SHED — (workloadId=ad25cf65-7e45-4680-b89b-a2ba7c61b3a8_1_0_sync)
2026-02-20 22:51:29 platform INFO APPLY Stage: CHECK_STATUS — (workloadId=ad25cf65-7e45-4680-b89b-a2ba7c61b3a8_1_0_sync)
2026-02-20 22:51:29 platform INFO No pod found running for workload ad25cf65-7e45-4680-b89b-a2ba7c61b3a8_1_0_sync
2026-02-20 22:51:29 platform INFO APPLY Stage: MUTEX — (workloadId=ad25cf65-7e45-4680-b89b-a2ba7c61b3a8_1_0_sync)
2026-02-20 22:51:29 platform INFO Mutex key: ad25cf65-7e45-4680-b89b-a2ba7c61b3a8 specified for workload: ad25cf65-7e45-4680-b89b-a2ba7c61b3a8_1_0_sync. Attempting to delete existing pods...
2026-02-20 22:51:29 platform INFO Mutex key: ad25cf65-7e45-4680-b89b-a2ba7c61b3a8 specified for workload: ad25cf65-7e45-4680-b89b-a2ba7c61b3a8_1_0_sync found no existing pods. Continuing...
2026-02-20 22:51:29 platform INFO APPLY Stage: ARCHITECTURE — (workloadId=ad25cf65-7e45-4680-b89b-a2ba7c61b3a8_1_0_sync)
2026-02-20 22:51:29 platform INFO APPLY Stage: LAUNCH — (workloadId=ad25cf65-7e45-4680-b89b-a2ba7c61b3a8_1_0_sync)
2026-02-20 22:51:29 platform INFO [initContainer] image: airbyte/workload-init-container:2.0.1 resources: ResourceRequirements(claims=[], limits={memory=2Gi, cpu=1}, requests={memory=2Gi, cpu=1}, additionalProperties={})
2026-02-20 22:51:29 platform INFO Launching replication pod: replication-job-1-attempt-0 (selectors = {}) with containers:
2026-02-20 22:51:29 platform INFO [source] image: airbyte/source-declarative-manifest:7.10.1 resources: ResourceRequirements(claims=[], limits={memory=2Gi, cpu=1}, requests={memory=1Gi, cpu=0.5}, additionalProperties={})
2026-02-20 22:51:29 platform INFO [destination] image: airbyte/destination-dev-null:0.9.3 resources: ResourceRequirements(claims=[], limits={memory=2Gi, cpu=1}, requests={memory=1Gi, cpu=0.5}, additionalProperties={})
2026-02-20 22:51:29 platform INFO [orchestrator] image: airbyte/container-orchestrator:2.0.1 resources: ResourceRequirements(claims=[], limits={memory=2Gi, cpu=1}, requests={memory=2Gi, cpu=1}, additionalProperties={})
2026-02-20 22:52:07 platform INFO Attempting to update workload: ad25cf65-7e45-4680-b89b-a2ba7c61b3a8_1_0_sync to LAUNCHED.
2026-02-20 22:52:07 platform INFO Pipeline completed for workload: ad25cf65-7e45-4680-b89b-a2ba7c61b3a8_1_0_sync.
2026-02-20 22:52:48 replication-orchestrator INFO Running replication worker...
2026-02-20 22:52:48 replication-orchestrator INFO Starting replication worker. job id: 1 attempt: 0
2026-02-20 22:52:48 replication-orchestrator INFO 
2026-02-20 22:52:48 replication-orchestrator INFO ----- START REPLICATION -----
2026-02-20 22:52:48 replication-orchestrator INFO 
2026-02-20 22:52:48 replication-orchestrator INFO Running destination...
2026-02-20 22:52:48 replication-orchestrator INFO Writing messages to protocol version 0.2.0
2026-02-20 22:52:48 replication-orchestrator INFO Reading messages from protocol version 0.2.0
2026-02-20 22:52:48 replication-orchestrator INFO Closing io.micronaut.context.propagation.instrument.execution.ContextPropagatingExecutorService@5fbbe7aa
2026-02-20 22:52:48 replication-orchestrator INFO Closing io.micronaut.context.propagation.instrument.execution.ContextPropagatingExecutorService@29911ee3
2026-02-20 22:52:48 replication-orchestrator INFO Closing io.airbyte.container.orchestrator.worker.io.LocalContainerAirbyteDestination@5ce4c15a
2026-02-20 22:53:49 replication-orchestrator WARN Failed to wait for exit value file /dest/exitCode.txt to be found.
2026-02-20 22:53:49 replication-orchestrator ERROR Error closing resource io.airbyte.container.orchestrator.worker.io.LocalContainerAirbyteDestination@5ce4c15a; recording failure but continuing.
2026-02-20 22:53:49 replication-orchestrator INFO Closing io.airbyte.container.orchestrator.worker.io.LocalContainerAirbyteSource@4d99d7ac
2026-02-20 22:53:49 replication-orchestrator INFO Closing io.airbyte.container.orchestrator.worker.RecordSchemaValidator@5722c149
2026-02-20 22:53:49 replication-orchestrator INFO Closing io.airbyte.container.orchestrator.persistence.SyncPersistenceImpl@58cb1f78
2026-02-20 22:53:49 replication-orchestrator ERROR Killing orchestrator because of an Exception
2026-02-20 22:53:50 platform INFO 
----- START POST REPLICATION OPERATIONS -----

2026-02-20 22:53:50 platform INFO No post-replication operation(s) to perform.
2026-02-20 22:53:50 platform INFO 
----- END POST REPLICATION OPERATIONS -----

---

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

Connector YAML:

version: 7.0.4

type: DeclarativeSource

check:
type: CheckStream
stream_names:
- posts

streams:

• type: DeclarativeStream
  name: posts
  primary_key:
  • id
    retriever:
    type: SimpleRetriever
    record_selector:
    type: RecordSelector
    extractor:
    type: DpathExtractor
    field_path: []
    requester:
    type: HttpRequester
    url_base: https://jsonplaceholder.typicode.com
    path: /posts
    http_method: GET
    request_parameters:
    _limit: "10"
    paginator:
    type: DefaultPaginator
    page_token_option:
    type: RequestOption
    inject_into: request_parameter
    field_name: _page
    pagination_strategy:
    type: PageIncrement
    page_size: 10
    start_from_page: 1

spec:
type: Spec
connection_specification:
type: object
$schema: http://json-schema.org/draft-07/schema#
required: []
properties: {}
additionalProperties: true

metadata:
testedStreams:
posts:
streamHash: ad11f9fa446b445a056b0f48d54e74059e0bc977

concurrency_level:
type: ConcurrencyLevel
default_concurrency: 1

[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/bd7b9f58f0c74a309ec57e2071829a46

✅ Devin AI session created successfully!

[devin-ai-integration]

Hi Sankalp Gupta (@dev-sankalp), thank you for reporting this issue!

I can see that your custom declarative source sync is failing with the error Failed to wait for exit value file /dest/exitCode.txt, followed by the orchestrator being killed. This is happening on both Airbyte Cloud and self-hosted v2.0.1, which suggests a platform-level issue rather than something specific to your environment.

From the logs, it appears the destination container (destination-dev-null:0.9.3) is crashing or exiting before it can write its exit code file. The replication orchestrator then fails because it cannot find /dest/exitCode.txt, and the "Streams without a status message: [posts]" error is a downstream consequence of this failure.

A few clarifying questions:

1. Does this happen with all custom declarative sources, or only this specific one? Have you tried syncing a built-in (non-custom) source to the same destinations?
2. Could you share the YAML manifest for the custom source (with any sensitive information like API keys removed)?
3. When testing on Airbyte Cloud, did you test with the same destination types (Azure Blob Storage, dev/null)?

I have escalated this to the internal team for further investigation.

Troubleshooting Steps (while waiting for investigation)

• Try creating a minimal declarative source with a single simple stream to narrow down the issue
• Check if the Kubernetes pod logs for the destination container show any startup errors (for self-hosted): kubectl logs <pod-name> -c destination
• Verify that your self-hosted deployment has sufficient resources — though with 16GB RAM this should not be a concern

---

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

This message is generated from Devin.ai (internal session link).

[devin-ai-integration]

This issue has been escalated to the internal team for investigation: https://github.com/airbytehq/oncall/issues/11382

This message is generated from Devin.ai (internal session link).