Save a custom record with its files
What It Does
A record save prepares attachments before opening its persistence transaction. The committed record then includes validated values, naming, reservations and the corresponding audit, history and supported event.
The Flow
When Something Fails
Reject the save at the property and abandon prepared copies when any preparation fails. Uncommitted copies remain because Platform lacks cleanup deployment. Roll back on invalid values, references, uniqueness, preparation or concurrency; abandon prepared copies. The earlier record is preserved, with abandoned storage copies outside its transaction. Ignore a failed nudge and rely on a later successful scheduled run. Delivery waits in the outbox without a maximum latency guarantee.
Open Design Questions
Deploying Platform asset cleanup remains necessary to complete the attachment lifecycle.