For what it’s worth, if it helps you troubleshoot or notice a pattern, Dropbox (and any of the other file-based services Drafts works with) has no API for appending-prepending. To do this Drafts actions:
- Figure out the dynamic path/file name for the action.
- Query the API to download the current version of that file.
- If that file does not exist (previous step fails), upload as a new file
- If that file does exist, read its contents, update it and upload the new version of the full content.
In the case of Dropbox, when the existing file is downloaded, it includes a revision number for the file, and that revision number is included with the call to update the file. In theory, if the revision number of the file has changed since the download (which is rare, it was moments earlier), Dropbox should (based on the parameters Dropbox sends) throw an error and not update the file because of conflict.
It appears, in some cases, Dropbox is treating the uploaded version as a conflict, and autorenaming it as if Drafts had passed different parameters.