Declarative schedules show per-env in the dashboard and each env counts towards your limit

[samejr]

If you define the cron patterns directly in your code (cron: "* * * * *") (a declarative schedule) we treat them as separate schedules so they can be disabled/deleted separately in different environments.

It's confusing though that they all show up in the schedules table in the dashboard per-environment and each environment counts as +1 towards your schedules limit.

We should change this so a declarative schedule is unique to the task ID, so it is only counted as +1 of your schedules limit across all environments.

[CodeMan62]

Can you provide a bit more info on this issue so i can work on it or take a look into it

[samejr]

This issue is still being debated as there's a few ways we could do it so it's hard to define at the moment. I think we'll end up folding this work into another bigger change we're making.

[CodeMan62]

@samejr Thanks for the update! I understand this is being considered as part of a larger change. Please let me know if there's anything I can help with once the direction is more clearly defined.

[matt-aitken]

@CodeMan62 we changed the way we count these now so it's more generous.