Skip to content

migration_import — events

Emitted

EventWhenPayload
migration.job.startedBackgroundTask enters executingjob_id, clinic_id
migration.job.completedPipeline ran to the endjob_id, clinic_id, total_entities, warnings_count
migration.job.failedUnhandled exception in the pipelinejob_id, clinic_id, error
migration.binary.resolvedSync agent uploaded a binary that matched a staging rowjob_id, staging_id, document_id

Plus every event published naturally by the mapped target services — patient.created, payment.recorded, document.uploaded, etc. The importer does not suppress them: downstream modules (patient_timeline, recalls, …) get the same signal they would for a manually-created entity. This is intentional.

Internal

EventProducerConsumerPurpose
migration.entity.persistedevery mapperevents.on_appointment_created_for_progressBumps processed_entities for the progress UI.

Consumed

None outside the internal migration.entity.persisted signal above.