Platform Data Jobs
What This Service Is For
Platform supplies input-file transfer and migration-package coordination. It also adopts the engine for its own field definitions and custom records, using bounded request execution.
Boundary
Uploads and migration runs belong to this service contract. Hosted engine records use the shared designs, while metadata retains its business records and saves. Workspace lifecycle remains responsible for loading and release.
Operations in Words
Upload authority covers opening, signing, reading, completing, aborting and listing transfers. Staff system authority covers run registration, inspection and driving controls; reading a running parent can advance it. Custom-field jobs include keyed reconciliation, while custom-record jobs omit that lookup. Neither supports rollback or publishes a Submissions binding.
Events and Jobs
Local requests run engine batches after commit. Lifecycle participants remove engine and package records according to reset or deletion intent. The module declares no business event or model invocation.
Consistency Guarantees
Run registration is atomic within the database. Storage completion, child submission, parent progress and local batch execution have separate boundaries. Interrupted requests and unrecorded remote submissions remain recovery gaps.