Log an activity with its links, files and follow-up
What It Does
Interaction logging commits the interaction, its owned links and file entries, and any requested follow-up together. File preparation precedes that transaction, so record atomicity does not include the prepared copies. Creation recovery uses the same retained identifier while the created row exists.
The Flow
The numbered hops specify the request, persistence and integration boundaries in order. Each hop identifies its evidence anchor, synchronization seam and observable failure outcome. Branches distinguish optional and delegated paths.
When Something Fails
Validation, missing references and follow-up failures refuse the entire record save. Enabled attention also participates in a follow-up’s transaction and can prevent logging. An ambiguous network response requires recovery because a committed result may already exist; shared asset cleanup behavior beyond the local submission remains unverified.
Open Design Questions
Product must settle the calendar anchor for suggested follow-ups and the meaning of an explicit No Owner selection during creation.