topic Error 'Max retries exceeded with url: /api/get_equipment' in BIM 360 API Forum

Error 'Max retries exceeded with url: /api/get_equipment'

Anonymous — Sun, 12 Nov 2017 22:30:08 GMT

Do you know what will cause the Error 'Max retries exceeded with your API call' (see below) ?

I posted this question few weeks ago before here but it disappears.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Exception Error when running API to grab Equipment's file-attachment !
Error (REQUEST): HTTPSConnectionPool(host='bim360field.autodesk.com', port=443):

Max retries exceeded with url: /api/get_equipment

(Caused by ProxyError('Cannot connect to proxy.', error("(104, 'ECONNRESET')",)))

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This error doesn't happen for those situation when API calls are made with low returned numbers of records.

The answer I got previously was like "it's Common error, go check Stackoverflow ourselves'.

But as it will work some time for small returned dataset, this is not a syntax error but a runtime error.

Please let me know how to resolve this error.

thanks & appreciate it !!

Re: Error 'Max retries exceeded with url: /api/get_equipment'

Anonymous — Tue, 14 Nov 2017 15:37:07 GMT

I found the reason, it is because of the limit of inflow data-size in our proxy.

Instead of one single API call for returning all EQUIPMENT's attachment data of one project,

i need to break it down as a loop with parameters offset & limit set as 30.

The reason 'Max retries exceeded' is definitely misleading.

Re: Error 'Max retries exceeded with url: /api/get_equipment'

anil_mistry — Wed, 15 Nov 2017 15:00:11 GMT

Hi @Anonymous,

Thank you for your reply and I am glad to hear that the issue is now resolved. Please, let us know if you have any other questions or concern.

Thank you and have a great day!

Re: Error 'Max retries exceeded with url: /api/get_equipment'

Anonymous — Mon, 18 Dec 2017 21:31:45 GMT

Even I have found the solution is to use the parameters 'limit' & 'offset' to solve most of this error,

however, I still occasionally receive this error by random for other API that doesn't need parameters 'limit' & 'offset'.

So I still have deep concern about the stability your API end-points. And very frustrated.

I can close this ticket since I have submitted a separate ticket to address the unreliability of your API behaviors.