To avoid request flooding that would impact all users and accounts, there is a maximum limit of 10 job status requests per minute per account.

When you submit a job via the API, you will receive a JobID. The status of a job can be requested by submitting JobID via the API. If you have multiple jobs that have been submitted, you can request the status of a list of JobIDs in a single request.

Jobs can be queued for some time for many reasons. The Language Studio queue allows for one or thousands of jobs to be queued for a single engine or many engines. In order to use resources efficiently there are some default limitations for the number of concurrent jobs that can run per account and the number of concurrent jobs that can run per engine.

Depending on how quickly you are updating the screen or database on the client side, you may want to update your display. We recommend that the minimum duration between requests be 10 seconds, but typically if you are not updating a live display, the duration should be around 60 seconds and if possible, all jobs that you are interested in should be requested in a single call to the API rather than individual calls for each JobID.

If you send too many requests within a short period of time, Language Studio will reject your request as it will be considered as data flooding. In such a case, you will receive the following error message:

“Too many requests within 1 minute. Please consider using the call back feature or request multiple job status feature.”

After 1 minute, you will be able to make requests again.