Connector Improvement: Optimize Slack Connector Channel Sync to Filter by Custom App Membership
Answered
Hi Team,
Problem: The initial and subsequent data syncs for the Slack connector are consistently taking up to 18 hours to complete. This extended sync duration is significantly impacting our project timeline and feature implementation.
Root Cause (Suspected): We understand that the connector currently fetches the entire list of Slack channels via the API, regardless of whether the custom Fivetran-managed Slack app has been added to them. We suspect this broad API call is the primary cause of the excessive sync time.
Requested Change: Modify the Slack connector's channel fetching logic to query and sync only the channels where the custom Slack application is an active member.
Priority: High. This performance issue is a blocking factor for current feature implementation and requires urgent attention.
Regards,
Sreejith
-
Official comment
Hi Sreejith,
Thank you for raising this sync improvement request. Your concern is valid and we do skip the channels where the app is not part of and it might some more api calls. We will do feasibility and see what ways we can improve this and improve the sync performance.
Can you please share more information about your use case and the sync time expected for it to be feasible ?
Thank You,
Vishal
-
Hi Fivetran Team,
Suhas from your support team indicated in ticket #318492 that development for this feature request was projected to begin in December 2025. Could you share the latest status of this request?
Regards,
Sreejith
-
Hi Sreejith,
This is in our backlog and has been prioritized to be picked. We are tentatively targeting to make the change by late Dec/ early Jan. I will keep you posted here when it is made available.
Thank You,
Vishal
Please sign in to leave a comment.
Comments
3 comments