Dropbox Cursor Behavior

Isn't this /2/files/list_folder/get_latest_cursor for polling in a continuous session and you cannot go backwards in time? My program is not limited to one continuous session; hence the approach is to save the cursor in a database for example, and then I can adjust my scan schedule.

Here is the snippet from Dropbox article, Detecting Changes.

Polling

As a result of this property of folder cursors, storing the cursor value allows you to poll for changes to the target directory. Folder cursors are long-lived, but may expire if unused for an extend time. Thus, while polling, be sure to always update to the latest returned cursor - even if no results are returned. A call to continue with an expired cursor will return a 409 reset error. This indicates you should issue a new call to /files/list_folder and iterate to obtain a new cursor. If the folder itself that the cursor refers to is deleted, the call will return a 409 path error. If your application is only interested in changes going forward, the /files/list_folder/get_latest_cursor will return the most recent cursor, without needing to iterate through list and continue calls.