@kapa.ai - when https://github.com/airbytehq/airbyte/issues/74378 will be addressed ? It causes all Iterable connector users on community and enterprise data consistency issues.

The knowledge sources do not mention any ETA or planned release version for fixing issue #74378, so I can’t say when it will be addressed. From the issue thread, we know: • The problem has been confirmed as a legitimate bug in how

source-iterable

handles the end boundary of incremental sync windows, leading to potential permanent data loss near the trailing edge of the window. [Iterable bug analysis] • The issue has been explicitly escalated to the internal engineering team and is tracked internally at

oncall/issues/11563

. [Iterable escalation] However, there is no statement about timelines, target versions, or a workaround being released yet in the provided materials. Given the impact you describe (data consistency issues for all Iterable connector users), the most effective next steps are: • Comment directly on the GitHub issue with your use case and impact to help prioritize it. [Iterable escalation] • If you’re an Airbyte Cloud or Enterprise customer, open a support ticket referencing the issue URL and the internal tracking ID (

oncall/issues/11563

) to get official status and prioritization. [Iterable escalation] I’m limited to what’s in the shared knowledge sources, so for any up‑to‑date ETA you’ll need to check the GitHub issue or contact Airbyte support. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.