fix(source-intercom): improve scroll concurrency error#78017
fix(source-intercom): improve scroll concurrency error#78017devin-ai-integration[bot] wants to merge 2 commits into
Conversation
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. 💡 Show Tips and TricksPR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
📚 Show Repo GuidanceHelpful Resources
|
|
|
Deploy preview for airbyte-docs ready!
Deployed with vercel-action |
|
↪️ Triggering Reason: Draft source-intercom scroll-error fix PR has CI passing and no |
|
Fix Validation EvidenceStatus: Fix/Feature Proven Successfully. I found sufficient regression evidence that this PR changes the Companies scroll-concurrency message on the real affected path without introducing unexpected command or protocol differences. Summary
EvidenceRegression attempt 3 used the privately reported affected connection in isolated comparison mode with only the affected
Observed behavior difference:
This satisfies the proving criteria: the target version surfaces the intended new Companies scroll message on the affected error path, while the surrounding behavior remains consistent with the published control version. Attempts
RecommendationReady for maintainer review/merge from a fix-validation standpoint. No live connection pinning was needed because isolated comparison regression testing reproduced the target error path and proved the intended message change. Suggested canary/e2e validation after merge: monitor Pre-flight Checks
|
|
What
Improve the Intercom Companies stream error message for HTTP 400 scroll concurrency failures.
Resolves https://github.com/airbytehq/airbyte-internal-issues/issues/16422
Related to https://github.com/airbytehq/oncall/issues/12575
How
HttpResponseFiltermessage withIntercom allows only one active company scroll per app.RETRYaction andtransient_errorclassification.source-intercomfrom0.13.22to0.13.23and updates the changelog.Review guide
airbyte-integrations/connectors/source-intercom/manifest.yamlairbyte-integrations/connectors/source-intercom/metadata.yamldocs/integrations/sources/intercom.mdUser Impact
Users should see a concise Intercom-specific message instead of a verbose retry/backoff message for Companies scroll concurrency failures.
Can this PR be safely reverted and rolled back?
Link to Devin session: https://app.devin.ai/sessions/fbed94f0038b405e96d866a04e1daca9