<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic list_folder/continue for file id in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/list-folder-continue-for-file-id/m-p/191327#M8356</link>
    <description>&lt;P&gt;The list_folder/continue api is needed for an API user to track changes to files under a given&amp;nbsp;folder. If the folder is moved, the list_folder/continue API will return a path not found error. If the id of the folder is known, the changes watching can be started again on the same folder via a call to get_metadata to get the file's path, then list_folder/continue with the file path. However, any changes that occur&amp;nbsp;between&amp;nbsp;when the folder is&amp;nbsp;moved, and when the new list_folder/continue call is made will be lost. This is really bad for anybody that relies on the list_folder/continue api for maintaining the consistency of their local state.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I ran the following experiment:&lt;/P&gt;&lt;P&gt;1. Create a folder and start watching changes via&amp;nbsp;&lt;SPAN&gt;list_folder/continue&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2. Add a file to the folder.&amp;nbsp;&lt;SPAN&gt;list_folder/continue shows the new file change.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;3. Move the folder to another location.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;4. list_folder/continue returns path not found.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;5. Add a file to the folder in the new location.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;6. Move the folder back to its original location.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;7. Call&amp;nbsp;&lt;SPAN&gt;list_folder/continue again. The new file, and the file added to the folder when it was in the different location&amp;nbsp;are listed.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;From this experiment I can conclude the&amp;nbsp;&lt;SPAN&gt;list_folder/continue api is independent of folder location. It is only time based.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;On my assumption that&amp;nbsp;&lt;SPAN&gt;list_folder/continue is time based, can you allow us to supply a 'from' parameter that will list folder changes from a given point in time?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;Alternatively, can you make the&amp;nbsp;&lt;SPAN&gt;list_folder/continue api support access by file ids so that we don't lose track of changes when a folder is moved, &lt;A href="https://blogs.dropbox.com/developers/2015/11/dropbox-api-v2-launches-today/" target="_self"&gt;as was one of the purported major features of api v2&lt;/A&gt;.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 29 May 2019 09:29:07 GMT</pubDate>
    <dc:creator>Jackson D.1</dc:creator>
    <dc:date>2019-05-29T09:29:07Z</dc:date>
    <item>
      <title>list_folder/continue for file id</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/list-folder-continue-for-file-id/m-p/191327#M8356</link>
      <description>&lt;P&gt;The list_folder/continue api is needed for an API user to track changes to files under a given&amp;nbsp;folder. If the folder is moved, the list_folder/continue API will return a path not found error. If the id of the folder is known, the changes watching can be started again on the same folder via a call to get_metadata to get the file's path, then list_folder/continue with the file path. However, any changes that occur&amp;nbsp;between&amp;nbsp;when the folder is&amp;nbsp;moved, and when the new list_folder/continue call is made will be lost. This is really bad for anybody that relies on the list_folder/continue api for maintaining the consistency of their local state.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I ran the following experiment:&lt;/P&gt;&lt;P&gt;1. Create a folder and start watching changes via&amp;nbsp;&lt;SPAN&gt;list_folder/continue&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2. Add a file to the folder.&amp;nbsp;&lt;SPAN&gt;list_folder/continue shows the new file change.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;3. Move the folder to another location.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;4. list_folder/continue returns path not found.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;5. Add a file to the folder in the new location.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;6. Move the folder back to its original location.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;7. Call&amp;nbsp;&lt;SPAN&gt;list_folder/continue again. The new file, and the file added to the folder when it was in the different location&amp;nbsp;are listed.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;From this experiment I can conclude the&amp;nbsp;&lt;SPAN&gt;list_folder/continue api is independent of folder location. It is only time based.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;On my assumption that&amp;nbsp;&lt;SPAN&gt;list_folder/continue is time based, can you allow us to supply a 'from' parameter that will list folder changes from a given point in time?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;Alternatively, can you make the&amp;nbsp;&lt;SPAN&gt;list_folder/continue api support access by file ids so that we don't lose track of changes when a folder is moved, &lt;A href="https://blogs.dropbox.com/developers/2015/11/dropbox-api-v2-launches-today/" target="_self"&gt;as was one of the purported major features of api v2&lt;/A&gt;.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:29:07 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/list-folder-continue-for-file-id/m-p/191327#M8356</guid>
      <dc:creator>Jackson D.1</dc:creator>
      <dc:date>2019-05-29T09:29:07Z</dc:date>
    </item>
    <item>
      <title>Re: list_folder/continue for file id</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/list-folder-continue-for-file-id/m-p/191425#M8365</link>
      <description>&lt;P&gt;Hi Jackson, this endpoint isn't time based exactly; when you supply a path it acts as a sort of filter on the events you'll get back. Suffice to say though, the behavior you described is expected, and the best way to handle that case would be file ID support for /files/list_folder, so I'm sending this along as a request for that. (If you need to stay up to date with the full state though, you should&amp;nbsp;use the root "" path.)&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2016 17:34:34 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/list-folder-continue-for-file-id/m-p/191425#M8365</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2016-10-20T17:34:34Z</dc:date>
    </item>
  </channel>
</rss>

