nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Child Item

Webhooks delay

Dinesh R.2

We have been using webhooks in our app for processing changes to a user's library. We have run into an issue with the v2 /list_folder/continue with cursor calls.

Whenever we get a user_id from webhooks, our app makes a call to the list_folder/continue API with the most recent cursor for the user (which we persist in our backend store). However, whenever we make this call we invariably get no entries back. We have noticed that we need to add a delay of 5 seconds or more to get the entries back.

I am wondering why there is such a noticeable lag to get the changes to a user's library. Also, our app is a "development" dropbox app. Would apps with "production" status have a more responsive experience when processing dropbox changes?

Find more posts tagged with

API

Abuse

Comments

Greg-DB

Production status wouldn't help here, as that just enables more users to connect to your app.

Are you using include_media_info=true when you originally get these cursors though?

Dinesh R.2

That is correct. We need the media info.

Greg-DB

Thanks! That's likely the cause here then. The media information can take some time to generate, before which the entries can't be returned for these cursors. We're always working to keep these delays to a minimum, but they can vary. Unfortunately I don't have a perfect solution to offer here, but you may want to just automatically retry after a little time when this happens.

Dinesh R.2

ok, thanks, Gregory! That makes sense. An automatic retry is what am planning to do for now, but it would be great if you could improve the experience at some point.