Trados Studio
Trados Enterprise
Trados Team
Trados GroupShare
Trados Business Manager
Passolo
MultiTerm
RWS AppStore
Connectors
Beta Groups
Managed Translation
MultiTrans
TMS
WorldServer
Language Weaver
Language Weaver Connectors
Language Weaver Edge
Tridion Docs
Tridion Sites
LiveContent S1000D
XPP
Language Developers
Tridion Docs Developers
Community Help
RWS User Experience
Internal Trados Ideas Community
Mercury
RWS Community Internal Group
RWS Training & Certification
Style Guides
RWS Campus
RWS Enterprise Technology Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Nordic Tridion Docs User Group
Tridion West Coast User Group
Trados Studio Ideas
Trados GroupShare Ideas
Trados Team Ideas
Trados Team Terminology Ideas
Trados Enterprise Ideas
Trados Business Manager Ideas
MultiTerm Ideas
Passolo Ideas
RWS Appstore Ideas
Tridion Docs Ideas
Tridion Sites Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
Managed Translation - Enterprise Ideas
TMS Ideas
WorldServer Ideas
LiveContent S1000D Ideas
Contenta S1000D
XPP Ideas
Events & Webinars
To RWS Support
Detecting language please wait for.......
For an SDL TMS job containing more than 250 tasks, GET GET v1/jobs/inbox from TMS API only returns 250 tasks and a 206 response. Is there a way to get the remainder of the tasks or is there another API call that we should be using instead?
Hi Octavio,
There is a default limit of 250 tasks imposed by SDL TMS to prevent performance degradation through heavy API usage. There is a setting called API_Max_Fetch which can be adjusted to allow you to return more results. This setting is held in the database and can be modified by an administrator; it can't currently be set through the UI.
I hope this helps,
David
Thank you very much for that information David. I will work with support to have them increase that setting to handle larger jobs. As a side question, is there a better way to handle this that would not require increasing that API_Max_Fetch setting? I am just wondering if we are doing this wrong and should have another approach to this.