From 4d172a1ffe4801afcfc1eda28f53a909f2b40796 Mon Sep 17 00:00:00 2001
From: hugocasa <hugo@casademont.ch>
Date: Fri, 1 May 2026 18:11:34 +0200
Subject: [PATCH] Revert "fix(cli): skip setScheduleEnabled when local YAML
 lacks `enabled`"

This reverts commit 23ba7e72fcbfc24711946e8fcd21b6a5a0faa769.
---
 cli/src/commands/schedule/schedule.ts | 10 +---------
 1 file changed, 1 insertion(+), 9 deletions(-)

diff --git a/cli/src/commands/schedule/schedule.ts b/cli/src/commands/schedule/schedule.ts
index 9ed1e1e4ec..37f8ac343d 100644
--- a/cli/src/commands/schedule/schedule.ts
+++ b/cli/src/commands/schedule/schedule.ts
@@ -153,15 +153,7 @@ export async function pushSchedule(
           ...preserveFields,
         },
       });
-      // Only push `enabled` when the local YAML actually carries it. Tarball
-      // export from a workspace fork strips the field (so fork→parent
-      // round-trips don't flip the parent's operational state), which means
-      // a sync push of fork-pulled YAMLs would otherwise call setEnabled
-      // with `enabled: undefined` and the backend would reject the body.
-      if (
-        localSchedule.enabled !== undefined &&
-        localSchedule.enabled !== schedule.enabled
-      ) {
+      if (localSchedule.enabled != schedule.enabled) {
         log.info(colors.bold.yellow(
           `Schedule ${path} is ${localSchedule.enabled ? "enabled" : "disabled"} locally but not on remote, updating remote`
         ));