Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Jira API call distribution/retry to stay within api rate limits

Answered
Jaffar Ahmad User

Jira has limited the number of requests possible per minute to maintain perfomance of Jira instances. Even if technically Jira provides means to increase those limits it is not advised or at least not carried out by many Jira admins due to performance concerns. Therefore a mitigation strategy within the Fivetran Jira connector is required. Be it a retry after receiving an api limit error or a deliberate distribution of api calls over time. Ideally this parameters can be configured by the user in Fivetran. e.g. [max api calls per minute], [max api calls per second].

 

Please sign in to leave a comment.

Comments

4 comments

Date Votes
  • Official comment
    Frank Fivetranner

    Hi Jaffar, 

    Our connector already has a retry strategy to retry when we encounter an api limit error. Can you be more specific about what issue you are facing? 

    Thanks, 

    Frank

  • Jaffar Ahmad User

    Hi Frank,

    would it be possible to at least exclude tables from being synced. especially the history tables, which cause a lot of unnecessary delay in syncing.

    We are unable to sync data within a reasonable timeframe (sync runs several days) for a small project in Jira. Although we only need a couple of information, all the history in the Jira project is being replicated.

    In addition, the retry strategy in the connector quickly switches to 5-minute wait times, causing additional delays.

    Kind regards,

    Jaffar

  • Frank Fivetranner

    Hi Jaffar, 

    Thanks for the reply. I will have our team look into these issues for you and get back. 

    Frank

  • Jaffar Ahmad User

    Hi Frank, 

    to facilitate the issue analysis on your end we also created an issue and gave access to the connector.

    Cheers,

    Jaffar