fix(source-intercom): Block simultaneous reading from companies endpoint#71141
Conversation
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. Helpful Resources
PR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
|
|
|
Deploy preview for airbyte-docs ready! ✅ Preview Built with commit c7d14c0. |
|
/ai-docs-review
|
|
/build-connector-images
|
|
/publish-connectors-prerelease
|
|
/ai-docs-review
|
Documentation ReviewOverall Assessment: The PR correctly implements a fix for concurrent API access issues but includes a changelog entry with an incorrect PR reference. The existing documentation does not mention the companies endpoint concurrency limitation, which could be valuable for users troubleshooting sync issues. High Priority (Correctness Issues)
Completeness Gaps
Readability/OrganizationDocumentation is well-organized and clear. No issues found. Style Nits
Summary of Recommended Changes
This review was generated by Devin. View session |
|
/publish-connectors-prerelease
|
|
/publish-connectors-prerelease
|
What
Resolves: https://github.com/airbytehq/oncall/issues/8346
Fixes API errors in source-intercom caused by duplicate concurrent requests to the companies endpoint. The issue occurred when the
companiesstream was being read both as a standalone stream and as a parent stream for substreams (likecompany_segments), resulting in simultaneous API calls that the Intercom API rejected.How
Added
block_simultaneous_read: "companies"to thecompaniesstream configuration inmanifest.yaml. This uses the new CDK feature (introduced in airbytehq/airbyte-python-cdk#870) that prevents streams with the same blocking group name from running concurrently.What happens now:
companiesis selected as a standalone stream, it runs normallycompaniesis used as a parent stream (for substreams), it's also marked activeReview guide
User Impact
Can this PR be safely reverted and rolled back?