diff --git a/docs/platforms/python/integrations/celery/crons.mdx b/docs/platforms/python/integrations/celery/crons.mdx
index 0e046b1679deb..df6e2d58a6453 100644
--- a/docs/platforms/python/integrations/celery/crons.mdx
+++ b/docs/platforms/python/integrations/celery/crons.mdx
@@ -30,6 +30,9 @@ app.conf.beat_schedule = {
     },
 }
 ```
+<Note>
+Please note that only crontab parseable schedules will be successfully upserted.
+</Note>
 
 Next, we need to initialize Sentry. Where to do this depends on how you run beat:
 - If beat is running in your worker process (that is, you're running your worker with the `-B`/`--beat` option), initialize Sentry in either the `celeryd_init` or `beat_init` signal.