Hello all, I’m currently using Airbyte to extract data from a single Monday.com board that contains approximately 49,000 rows. However, when running the sync through the Airbyte Monday connector, I consistently receive only around 33,000 rows. I have already attempted several troubleshooting steps, including: • Recreating the connector, both source and destination • Creating a new destination database Unfortunately, the issue persists. While reviewing the logs, I found the following pattern, which appears to point to the cause of the failure:

2026-03-03 12:05:56 replication-orchestrator INFO Records read: 20000 (46 MB)
2026-03-03 12:15:12 replication-orchestrator INFO Records read: 25000 (58 MB)
2026-03-03 12:24:22 replication-orchestrator INFO Records read: 30000 (70 MB)
2026-03-03 12:24:55 source ERROR Exception while syncing stream items
(...)
2026-03-03 12:24:55 source INFO During the sync, the following streams did not sync successfully: items: AttributeError("'NoneType' object has no attribute 'get'")
2026-03-03 12:24:55 source ERROR Concurrent read failure

It appears that the sync is failing resulting in incomplete extraction. Does anyone know how to address this issue or what may be causing the

NoneType

error within the Items stream? Any guidance or recommended next steps would be greatly appreciated. Thank you!

There isn’t a direct match for your exact

AttributeError("'NoneType' object has no attribute 'get'")

in the Monday items stream in the provided knowledge, but there are closely related Monday connector issues that suggest this is likely a connector/platform bug rather than a configuration problem on your side. Relevant points from the knowledge: • There is an open issue where the Monday source fails on the

items

stream with a JSON shape problem (

KeyError: 'data'

), causing sync failures and missing ~5k records. [KeyError data] • Multiple users report they “can’t manage to retrieve items” because of this error on recent Monday connector versions. [KeyError data] • Another Monday issue shows that some Monday API responses are rejected as “Invalid GraphQL request” due to how the request is built, which again is a connector/platform behavior, not user config. [Monday error] • The official docs confirm that

items

is a supported stream and that incremental sync for

items

depends on

activity_logs

, but they don’t document your specific

NoneType

error. [Monday streams] Given that: 1. You consistently get fewer rows than exist on the board. 2. The failure happens mid‑sync on the

items

stream. 3. Similar Monday

items

issues are already tracked as connector/platform bugs. the most likely explanation is that you’re hitting a known (or closely related) Monday connector/platform bug in the

items

stream, not a misconfiguration. Recommended next steps 1. Check your Monday source connector version and compare it with the changelog to see if you’re on a version that has known issues with

items

. [Monday changelog] ◦ If you’re not on the latest compatible version for your Airbyte instance, upgrade the Monday source and re‑run the sync. 2. Try a Full Refresh (not Incremental) for the

items

stream once, to rule out state-related issues. (Docs confirm

items

supports both modes.) [Monday streams] 3. If the problem persists after upgrading and running a Full Refresh: ◦ Open or update a GitHub issue for

source-monday

and attach: ▪︎ Your connector version, Airbyte version, deployment type. ▪︎ The failing logs (including the

NoneType

stack trace). ▪︎ The fact that you’re missing ~16k rows from a ~49k-row board. ◦ Reference the existing

KeyError: 'data'

issue so the team can see it’s another failure mode in the

items

stream. [KeyError data] Because the knowledge sources don’t include this exact

NoneType .get

stack trace, I can’t point to a confirmed fix, only to strongly related Monday

items

issues that have been escalated to the platform/connector teams. [KeyError data; Monday error] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai is there any known issue regarding incomplete data extraction?

Yes, there are known issues related to incomplete data extraction from the Monday

items

stream. 1. KeyError: 'data' in

items

pagination An open issue for

source-monday

shows syncs failing on the

items

stream with

KeyError: 'data'

when the connector tries to read

response.json()["data"]

during pagination, which leads to a “Concurrent read failure.” [KeyError data] ◦ The reporter explicitly mentions losing about 5k records during ingestion and suspects it’s related to this error. [KeyError data] 2. Items stream unable to finish Another (closed) issue reports that all Monday streams sync except

Items

, which repeatedly fails and loads no data, blocking their use case. [Items stream issue] 3. Platform / connector classification In the

KeyError: 'data'

issue, maintainers note that this appears to be a platform infrastructure error, not a simple configuration problem, and route it to the platform team. [KeyError data] So yes: based on the knowledge sources, there are known issues where the Monday

items

stream can fail mid‑sync and result in missing or incomplete data. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Hi @frederico_raposo I recently updated my monday source connector and this error started for me today as well for only 1 Monday board. I haven't tried this yet, but planning to downgrade my source connector because the same board worked a month ago. Do you have a workaround or source connector version that works?