We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
/list_folder/get_latest_cursor -> shared_link
Hello, I noticed that for get_latest_cursor you can add a shared_link parameter. If I understand the documentation correctly, this parameter allows you to get the cursor for a file whose name is cont...
I would need a cursor to be able to get the next files in the folder. For example, I have downloaded information (file name, etc.) about some of the files in the Dropbox folder. Information about files is downloaded to a file named x.jpg. I miss the cursor value. How can I get information about the next files in the Dropbox folder, but not from the beginning?
Hi maxior1234,
As far as you are correctly describing what you want, it's a cursor actually. As I mentioned cursor describe current enumeration state, nothing else. If the added files (past the last cursor) are not too much, you can add them to your sheet by hand and use the /2/files/list_folder/get_latest_cursor call (applied to containing folder, not to a file) to get the actual (latest in this case) cursor and continue further. Otherwise you have to start listing from beginning. To avoid such "incidents", review why you have lost your cursor and take measures (if changes in the file is the reason, keep/backup the cursor in alternative file for instance - don't rely on insecure storage).
Good luck.
Does cursor have any life expectancy? For example, it happens that tokens expire after a certain period of time, or is it similar with cursor?
No, no... Definitely not. Cursor doesn't expire. Just check why you have it lost (if you lost it, why you have doubts it expires 🧐)! Only this will let you fix the issue and avoid further "incidents". 😉 You may have some weaknesses in your application algorithm. Check this too.
I am wondering about one solution? Currently cursor saves in one place. Since I download information about files one at a time, it gets another cursor after each download. If I were to write cursor on the same line as the file information, maybe this would help to eliminate this situation. If so, I would always have the cursor either the last one, or at least before the last one. Separating the cursor from the rest is also good, but it doesn't rule out my mistake, for example. In the sense that I will accidentally replace it with the wrong cursor. I have some of the same automations that work the same but use different places in the dropbox. On the other hand, the option that I am writing about a moment earlier is more difficult to implement.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
