fix(deployment): correct deployment cancellation logic and ensure proper status update

- Updated the initCancelDeployments function to set the status of running deployments to 'cancelled' instead of 'error'.
- Reintroduced the call to initCancelDeployments in the server initialization process to ensure cancellations are handled correctly.

apps/dokploy/server/server.ts

@@ -43,6 +43,7 @@ void app.prepare().then(async () => {
 		if (!IS_CLOUD) {
 			setupDockerStatsMonitoringSocketServer(server);
 		}
+		await initCancelDeployments();
 
 		if (process.env.NODE_ENV === "production" && !IS_CLOUD) {
 			setupDirectories();
@@ -53,7 +54,6 @@ void app.prepare().then(async () => {
 			await migration();
 			await initCronJobs();
 			await initSchedules();
-			await initCancelDeployments();
 			await initVolumeBackupsCronJobs();
 			await sendDokployRestartNotifications();
 		}

packages/server/src/utils/startup/cancell-deployments.ts

@@ -7,8 +7,8 @@ export const initCancelDeployments = async () => {
         console.log("Setting up cancel deployments....");
 
     const result = await db.update(deployments).set({
-        status: "error",
-    }).where(eq(deployments.status, "cancelled"));
+        status: "cancelled",
+    }).where(eq(deployments.status, "running")).returning();
 
     console.log(`Cancelled ${result.length} deployments`);
     } catch (error) {