Child Item

/2/files/save_url/check_job_status

Hi!

My app calls /2/files/save_url then follows up the async upload with /2/files/save_url/check_job_status.

When dropbox responds with in_progress in .tag, it calls check_job_status later again.

When dropbox responds with complete, it stops.

When dropbox responds with failed, it starts from beginning calling save_url again, then checks job status (with the new job_id).

Sometimes it gets a failed response with error message: not_found, so it starts uploading again. However in the end there are many files in my dropbox folder:
fileName, fileName(1), fileName(2) ...

Q: Could there be an eventual inconsistency when check_job_status is called? Can I ever get a failed response when it should actually be in_progress?

I will try to call check_job_status with some delay to see if it solves the problem.

Thanks,

Győző

Find more posts tagged with

API

Abuse

Comments

Greg-DB

Hi Győző, the not_found error should indicate that "The file where the URL is saved to no longer exists". Is there any other activity in the account that might be causing this?

If not, meaning you're getting the not_found error when the file is successfully getting saved, and isn't being deleted or moved by something else, that sounds like a bug. In that case, please share some sample requests and responses (including response headers ideally, but please redact the access token) so that we can look into it. Thanks in advance!

Győző C.

Hi Greg,

no there is no other activity at the account.

Here are the logs:

08:52:27.261
logRequest: https://api.dropboxapi.com/2/files/save_url
Method: POST
Content-Type=application/json; charset=utf-8
Authorization=Bearer *****
{"url":"exampleSourceUrl","path":"/examplePath/exampleFile.xml"}

08:52:27.847
logResponse: Response code: 200
Server=nginx
Date=Fri, 04 Nov 2016 07:52:27 GMT
Content-Type=application/json
Content-Length=66
Connection=keep-alive
Cache-Control=no-cache
Pragma=no-cache
Set-Cookie=gvc=Mjg2NTYwNzExNzkzMTE0NzU5MjIwODMzNDQzNzk4MTcxNjIzOTY1; expires=Wed, 03 Nov 2021 07:52:27 GMT; httponly; Path=/; secure
User-Agent=
X-Content-Type-Options=nosniff
X-Dropbox-Http-Protocol=None
X-Dropbox-Request-Id=18f88d674bf00ed790992b9e09042e86
X-Frame-Options=SAMEORIGIN
X-Server-Response-Time=508
{".tag": "async_job_id", "async_job_id": "bKYP2ka871QAAAAAAAAEDg"}

08:52:29.198
logRequest: https://api.dropboxapi.com/2/files/save_url/check_job_status
Method: POST
Content-Type=application/json; charset=utf-8
Authorization=Bearer *****
{"async_job_id":"bKYP2ka871QAAAAAAAAEDg"}

08:52:29.330
logResponse: Response code: 200
Server=nginx
Date=Fri, 04 Nov 2016 07:52:29 GMT
Content-Type=application/json
Content-Length=23
Connection=keep-alive
Cache-Control=no-cache
Pragma=no-cache
Set-Cookie=gvc=Mzg4NzI0MzI0NzU1MDA1Mzk1MzU3NTk0MDU0MTM0ODgxNTM0OA%3D%3D; expires=Wed, 03 Nov 2021 07:52:29 GMT; httponly; Path=/; secure
User-Agent=
X-Content-Type-Options=nosniff
X-Dropbox-Http-Protocol=None
X-Dropbox-Request-Id=e3e87f3d39ea6393fcadd8639b4e87cd
X-Frame-Options=SAMEORIGIN
X-Server-Response-Time=71
{".tag": "in_progress"}

08:52:30.444
logRequest: https://api.dropboxapi.com/2/files/save_url/check_job_status
Method: POST
Content-Type=application/json; charset=utf-8
Authorization=Bearer *****
{"async_job_id":"bKYP2ka871QAAAAAAAAEDg"}

08:52:30.584
logResponse: Response code: 200
Server=nginx
Date=Fri, 04 Nov 2016 07:52:30 GMT
Content-Type=application/json
Content-Length=51
Connection=keep-alive
Cache-Control=no-cache
Pragma=no-cache
Set-Cookie=gvc=MTY5OTIxNjY5NzY5NzE5MzI2NDIwMzQ0MTgxOTE3MzA3MTIwMTYw; expires=Wed, 03 Nov 2021 07:52:30 GMT; httponly; Path=/; secure
User-Agent=
X-Content-Type-Options=nosniff
X-Dropbox-Http-Protocol=None
X-Dropbox-Request-Id=95472ff88291cb903b98ad70de27dffc
X-Frame-Options=SAMEORIGIN
X-Server-Response-Time=83
{".tag": "failed", "failed": {".tag": "not_found"}}

Greg-DB

Thanks! Can you share an actual URL and path (for the parameters to the intial call to /2/files/save_url) that reproduces this though? I can't reproduce this yet, so I suspect the specific values you're using may be relevant.

You can open a ticket here if you'd prefer to share privately:

https://www.dropbox.com/developers/contact

Thanks in advance!

Győző C.

Dear Greg,

I have opened a ticket and added the actual parameters there.

Thanks!

Greg-DB

This should be fixed now.