Check which released records reached the archive this month.
Neil
- Once the connection is configured, I’ll use the records it provides and cite each one. Anything it doesn’t supply stays listed as missing.
- Reads
Files in the folders in scope
- Returns
- Records sent, destinations and failed transfers
- Missing or unmatched information
- Next steps for your team to review
1What’s connected.
Exchange files between Dropbox and Seal through a connection set up with Seal’s API or Scripts. Agree which folders are in scope, which system holds the controlled version of each document and how changed or deleted files are handled.
Connection setup and permissions
Use Seal’s APIs or scripting engine for a connection tailored to your process. Agree the data mapping, access and direction of transfer before implementation.
2Exchange files between Dropbox folders and Seal.
Route
The files/upload endpoint creates a file from the request body, up to 150 MiB; larger files go through upload sessions.¹
Record identity
An upload returns a unique file ID and a rev for the current revision, which can be used to detect changes and avoid conflicts.¹ Each file’s metadata carries a content_hash, a SHA-256 over 4 MB block hashes, so an upload can be checked without downloading it.²
Revisions
The upload’s write mode decides what happens on a clash: add renames the new file by appending a number, overwrite always replaces, and update replaces only if the rev you send is still current. Writing identical content to the same path writes nothing.¹ files/list_revisions returns a file’s revisions and files/restore brings one back. Version history covers 30, 180 or 365 days, depending on the plan.³⁴⁵
When it fails
- Uploads are refused with 429
- On HTTP 429, an app should wait the number of seconds in Retry-After before trying again.¹ Queue the transfer and retry after that wait, keeping the Seal record and the Dropbox rev together.
- Someone edited a file Seal was about to replace
- In update mode, an upload replaces the file only if the rev sent is still the current one.¹ Upload in update mode with the rev Seal last read, so a newer edit in Dropbox is not overwritten.
- A deleted file is needed later
- Legal holds need the Data Governance Add-On on team accounts, and people on hold can still edit and delete files.⁶ Decide which system keeps the controlled version of each document before a folder comes into scope.
Check one record
Upload one controlled document from Seal into a test folder and compare its content_hash with Seal’s copy. Edit it in Dropbox, then confirm the next transfer reads the new rev and keeps both versions linked to the Seal record.
3Start with the job.
Tell us what Neil needs to do and which records it needs. We’ll confirm the interface, permissions and implementation scope with your team.
4Before it goes live.
Access and any write-back
Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.
