@kapa.ai I'm having issues with dynamodb connector, sometimes the sync works and sometimes I receive an error "message='Airbyte could not track the sync progress. Sync process exited without reporting status.', type='io.airbyte.workers.exception.WorkloadMonitorException', nonRetryable=false" after a very long sync time. (OSS Version)

This specific DynamoDB behavior (intermittent success, very long runs, and then

WorkloadMonitorException

/ “could not track the sync progress”) is not documented in detail in the provided sources, so I can only infer from related issues. From what we do have: - The

WorkloadMonitorException

error (

"Airbyte could not track the sync progress. Sync process exited without reporting status."

) is a generic platform-level error that appears when the worker process stops without properly reporting its status to Airbyte’s workload monitor, often after long or heavy syncs. [[Workload hanging](https://github.com/airbytehq/airbyte/issues/56926); [Workload monitor error](https://github.com/airbytehq/airbyte/issues/55812); [SP-API failure](https://github.com/airbytehq/airbyte/issues/53167)] - There is an open issue for DynamoDB checksum errors where the official guidance is that DynamoDB is not currently prioritized for improvements, and a user suggests exporting to S3 and then using the S3 connector as a workaround. [[Dynamo checksum issue](https://github.com/airbytehq/airbyte/issues/49805)] - DynamoDB also recently had an OOM issue fixed in a newer connector version. [[Dynamo OOM fix](https://github.com/airbytehq/airbyte/issues/61600)] Given these, the most grounded steps you can take based on the sources: 1. Upgrade platform and connector to latest versions Several “stuck” / “hanging” / long-running sync issues (not specific to DynamoDB) were either mitigated or first investigated by upgrading Airbyte and the connectors, as many platform improvements target job orchestration and long-running sync stability. [[Random hangs fixed by upgrade](https://discuss.airbyte.io/t/2308); [Support asking to upgrade for large sync cancels](https://discuss.airbyte.io/t/2921); [Similar intermittent failures, recommendation to upgrade](https://discuss.airbyte.io/t/2656)] Make sure: - Your Airbyte OSS version is current. -

source-dynamodb

is at least at or beyond the version where the OOM fix was merged (issue closed by PR #61601). [[Dynamo OOM fix](https://github.com/airbytehq/airbyte/issues/61600)] 2. Treat it as a long-running / heavy-sync stability issue Similar symptoms (jobs hanging or stalling on large/long-running syncs, then needing manual cancellation) appear with other connectors and destinations. [[S3 Data Lake long sync stall](https://github.com/airbytehq/airbyte/issues/56926); [EKS HubSpot syncs getting stuck](https://discuss.airbyte.io/t/3797)] While the sources don’t provide exact settings, they do suggest: - Job timeouts and job-related configuration may need tuning for long-running syncs. [[Timeout suggestion](https://discuss.airbyte.io/t/3171)] - Very large catalogs / many streams or large data volumes tend to trigger various stability issues; splitting data across multiple connections or reducing what is synced in a single job is often recommended. [[Many-tables causing failures](https://discuss.airbyte.io/t/2656); [No-code connector with many streams causing global issues](https://github.com/airbytehq/airbyte/issues/55812)] 3. Consider the documented DynamoDB workaround Since DynamoDB itself isn’t currently on the roadmap for improvements and has known issues, one user workaround is to export data from DynamoDB to S3 on a schedule and then use the S3 source connector (which is certified and more actively supported). [[Dynamo checksum issue](https://github.com/airbytehq/airbyte/issues/49805)] Because the sources do not provide a DynamoDB-specific fix for

WorkloadMonitorException

, I can’t point to an exact configuration change that will resolve your case. If, after: - updating Airbyte OSS and the DynamoDB connector, - tuning job timeouts / limits, and - reducing per-sync volume (fewer tables/streams or partitioning the data), you still see the same error, the most supported path in the current docs and issues is to either: - adopt the DynamoDB → S3 → Airbyte S3 connector pattern as a workaround, or - open a new GitHub issue for

source-dynamodb

including full logs and your config, referencing that you’re seeing

WorkloadMonitorException

on long-running syncs; this mirrors how others have surfaced similar platform-level issues. [[Dynamo checksum issue](https://github.com/airbytehq/airbyte/issues/49805); [All syncs hanging](https://github.com/airbytehq/airbyte/issues/55812)]