/files/import-from-url/async is broken

Hi,

We post 7 files in a CRON from a remote site to a HubSpot folder. The response for all of the files is a 202 which loosely translates as “we’ll get to your request at some point, but don’t count on it right away”. In other words, a 202 is different than a 200 because it’s only an acknowledgement of the request, it does not complete the request itself.

Therefore, for several minutes, maybe as long as 15 to 30 minutes, the uploaded file will return a 404 when we try to later access it. Note that the files we are uploading already exist with the same name, so we are updating existing files. Rather than a 404, isn’t there some way to see the last known version from cache?

So, in summary, can anyone explain the proper way to upload a file with the same name as an existing file so that it’s immediately available? And if it cannot be immediately available, is there a way to see the most recent version that was previously uploaded? It seems to us that the request causes the existing file to be deleted immediately, but the upload of the replacement might take several minutes.

Thanks in advance.

Hi, @CPopolo. Thanks for reaching out. Hey, @DarianVretenar @dannio @jpsanchez, do you have any experience here?

Thank you! — Jaycee

So I conclude that this functionality is broken and no one at HubSpot has any idea why.