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:
Summit Dental Care
2026-06-26 22:55:07 -04:00
parent 1edf73fdc8
commit 27d9132820
308 changed files with 2570 additions and 1816 deletions

View File

@@ -4,7 +4,9 @@ export const UserAggregateResultSchema = z.object({ _count: z.object({
username: z.number(),
password: z.number(),
autoBackupEnabled: z.number(),
autoBackupHour: z.number(),
usbBackupEnabled: z.number(),
usbBackupHour: z.number(),
patients: z.number(),
appointments: z.number(),
staff: z.number(),
@@ -28,18 +30,26 @@ export const UserAggregateResultSchema = z.object({ _count: z.object({
patientConversations: z.number()
}).optional(),
_sum: z.object({
id: z.number().nullable()
id: z.number().nullable(),
autoBackupHour: z.number().nullable(),
usbBackupHour: z.number().nullable()
}).nullable().optional(),
_avg: z.object({
id: z.number().nullable()
id: z.number().nullable(),
autoBackupHour: z.number().nullable(),
usbBackupHour: z.number().nullable()
}).nullable().optional(),
_min: z.object({
id: z.number().int().nullable(),
username: z.string().nullable(),
password: z.string().nullable()
password: z.string().nullable(),
autoBackupHour: z.number().int().nullable(),
usbBackupHour: z.number().int().nullable()
}).nullable().optional(),
_max: z.object({
id: z.number().int().nullable(),
username: z.string().nullable(),
password: z.string().nullable()
password: z.string().nullable(),
autoBackupHour: z.number().int().nullable(),
usbBackupHour: z.number().int().nullable()
}).nullable().optional()});