BDS0.1

Evidence

Understand file limits, persistence and what happens when an upload fails.

Reviewed 2026-10-28Markdown

Accepted input

The Slack modal accepts up to four newly selected files: PNG, JPG, JPEG, GIF, WebP or PDF. Each must be at most 5,000,000 bytes. requireEvidence is currently false. A future requirement can accept retained evidence on an edited response. Value currently accepts non-negative whole numbers because allowDecimalValue is false. These are workflow rules, not universal Airtable limits.

Storage sequence

  1. Save or update Observation as Processing.
  2. Request file metadata from Slack using the workspace bot.
  3. Validate the download host, extension and size.
  4. Download and upload the file into Evidence Files°.
  5. Confirm all new files were uploaded.
  6. Store Slack file IDs and source references, then set Recorded.

Files are deduplicated by Slack file ID, including IDs recovered from attachment filenames. The limit of four applies to each submission, not to total accumulated attachments. Existing evidence is retained.

Failure and recovery

A failed transfer can leave a saved value and partial attachments. Check Collection Status*, Collection Error and existing files before retrying. The workflow can mark a saved row Failed and notify the user. A later Slack message-update failure can also reach the failure handler after data was saved. Do not interpret a notification error as proof that no data exists.