#cant deploy due to schedule limits?

1 messages ยท Page 1 of 1 (latest)

elfin warren
#

Hi! I have 10 schedules set and when i deploy to prod i get this message: You have created 10/10 schedules so you'll need to increase your limits or delete some schedules.

So 9 is the max allowed for free plan? i dont mind about upgrading to pro plan, but i tought 10 was allowed for free plan.

split lily
#

You definitely should be getting 10. Do you have any other schedules set in other environments? Schedules set in Dev and Staging also count towards your 10 limit.

elfin warren
#

i got 10 in dev. So 10 + 10?

quiet walrus
#

A declarative schedule is when you define cron on your task like this:

export const firstScheduledTask = schedules.task({
  id: "first-scheduled-task",
  //every two hours (UTC timezone)
  cron: "0 */2 * * *",
  run: async (payload, { ctx }) => {
    //do something
  },
});

Each of these counts as a schedule for each environment. So if you have 10 tasks like this in dev, then pushing to prod will mean you have 20 schedules. They're separated by environment because you wouldn't want changes you make in DEV to impact your deployed schedules.

We increased the free plan limit from 3 to 10 when we introduced declarative schedules.

#

We should make this clearer than it is

elfin warren
#

ok thank you, will add my CC ๐Ÿ™‚

quiet walrus
#

Sorry we really need to do a better job of communicating this, I think it's confusing

elfin warren
#

Just to let you know. Migrated 34 v2 tasks to v3, Upgraded to pro plan then deployed to production. It's working like a charm! ๐Ÿ˜„

i still have 1 v2 task that use realtime notification, lazy to pool the db ๐Ÿ™‚ Will wait for your update!

You guys r0x!