fix: Start cronjobs after the database has been migrated

.changeset/lucky-wolves-turn.md

@@ -0,0 +1,5 @@
+---
+"@rocket.chat/meteor": patch
+---
+
+Fixes a UI issue that showed the incorrect migration number on the `Information` page. This was caused by a function calculating the stats before the server had migrated the database and updated the control.

apps/meteor/server/startup/cron.ts

@@ -1,5 +1,4 @@
 import { Logger } from '@rocket.chat/logger';
-import { Meteor } from 'meteor/meteor';
 
 import { federationCron } from '../cron/federation';
 import { npsCron } from '../cron/nps';
@@ -12,14 +11,13 @@ import { videoConferencesCron } from '../cron/videoConferences';
 
 const logger = new Logger('SyncedCron');
 
-Meteor.defer(async () => {
+export const startCronJobs = async (): Promise<void> => {
 	await startCron();
-
 	await oembedCron();
 	await usageReportCron(logger);
 	await npsCron();
 	await temporaryUploadCleanupCron();
 	await federationCron();
 	await videoConferencesCron();
-	await userDataDownloadsCron();
-});
+	userDataDownloadsCron();
+};

apps/meteor/server/startup/index.ts

@@ -1,6 +1,6 @@
 import './appcache';
 import './callbacks';
-import './cron';
+import { startCronJobs } from './cron';
 import './initialData';
 import './serverRunning';
 import './coreApps';
@@ -13,6 +13,8 @@ import { isRunningMs } from '../lib/isRunningMs';
 
 export const startup = async () => {
 	await performMigrationProcedure();
+
+	setImmediate(() => startCronJobs());
 	// only starts network broker if running in micro services mode
 	if (!isRunningMs()) {
 		require('./localServices');