fix: use in-memory startedAt for cron job log to survive DB restore
The auto-import wipes the database, destroying the cronJobLog record created at the start of the job. Now duration is calculated from a local variable instead of querying the DB, and if the record is gone a fresh log entry is created in the restored database. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Sonnet 4.6
parent
1edf73fdc8
commit
27d9132820
+2
@@ -25,7 +25,9 @@ const makeSchema = () => z.object({
|
||||
username: z.string(),
|
||||
password: z.string(),
|
||||
autoBackupEnabled: z.boolean().optional(),
|
||||
autoBackupHour: z.number().int().optional(),
|
||||
usbBackupEnabled: z.boolean().optional(),
|
||||
usbBackupHour: z.number().int().optional(),
|
||||
patients: z.lazy(() => PatientCreateNestedManyWithoutUserInputObjectSchema).optional(),
|
||||
appointments: z.lazy(() => AppointmentCreateNestedManyWithoutUserInputObjectSchema).optional(),
|
||||
staff: z.lazy(() => StaffCreateNestedManyWithoutUserInputObjectSchema).optional(),
|
||||
|
||||
Reference in New Issue
Block a user