From e869af1e7529a5e881334ea17f58e45155e08d24 Mon Sep 17 00:00:00 2001
From: Keith Brink <keith.brink@gmail.com>
Date: Fri, 28 Jul 2023 11:58:13 -0400
Subject: [PATCH] Update README.md

---
 README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/README.md b/README.md
index f9dc742..f55bcd5 100644
--- a/README.md
+++ b/README.md
@@ -146,6 +146,8 @@ This command is responsible for syncing your schedule with the database, and opt
 
 In a non-production environment you should manually run `schedule-monitor:sync`. You can verify if everything synced correctly using `schedule-monitor:list`.
 
+**Note:** Running the sync command will remove any other cron monitors that you've defined other than the application schedule.
+
 ## Usage
 
 To monitor your schedule you should first run `schedule-monitor:sync`. This command will take a look at your schedule and create an entry for each task in the `monitored_scheduled_tasks` table.