Skip to content

title: "Bulk import scheduling" description: "Bulk import execution is explicitly scheduled after a successful dry run." Scheduling controls when data is written to live tables and ensures that the syst...

Bulk import scheduling

Bulk import execution is explicitly scheduled after a successful dry run.
Scheduling controls when data is written to live tables and ensures that the system enters a controlled, write-locked state during execution.

Only one bulk import can exist at a time per system.

What can be scheduled

Bulk import scheduling applies to the execution phase of an import.

After a dry run has completed:

  • the import may remain unscheduled
  • the import may be scheduled for execution at a specific time
  • the import may be cancelled (deleted)

Scheduling does not modify the uploaded files or the dry run results.
It only determines when execution against live data begins.

Required fields

Bulk import scheduling does not introduce additional data fields.

The following prerequisites must be met before scheduling is allowed:

  • the ZIP file has passed structural validation
  • the dry run has completed
  • the import has not been cancelled

No file contents or configuration can be changed once execution starts.

Validation and rules interactions

During execution:

  • write rules are bypassed
  • only structural schema constraints apply
  • identifier and relation resolution follows the same logic as dry run

Execution runs with a system-wide write lock:

  • all other write operations are blocked
  • no API, UI, or background mutations are permitted
  • reads remain available

Execution is non-transactional across tables and files.

Common errors

Typical scheduling- and execution-related issues include:

  • attempting to create or schedule a second import while one already exists
  • row-level errors during execution due to:
  • unresolved identifiers
  • invalid data formats
  • relation resolution failures

Row-level errors do not stop execution and do not affect unrelated rows.

Once execution has started, it cannot be cancelled or rolled back.

Related concepts