Stop having the end date be required or at least have no default end date

I’m glad you made this - this also got me the other day, and it’s not just JO. I had a Data Designer where the end date defaulted to the same day for the refresh schedule.

In what world would I want to “regularly schedule” something for a single day?

I think platform-wide, the end date should not only be blank by default without causing error, but there should be an admin tool to globally review schedules for items, with configurable alerts.

You could have things show up as “active” but aren’t actually running, which is not something you can see as easily.

I also mentioned it as one of the reporting improvements I’d like to see on JO here: 

but really it should be in that sweet admin home we’ve been promised for years :)

I have been setting these 2099 when it will hopefully not be relevant anymore, but it’s a silly trick. If automation needs to be set to run for over 70 years, can we just call it “until instructed otherwise” and move on?

Thank you for validating, I was 75% sure it was Data Designer that I had run into this before!  It should be a principle applied throughout the platform.

YES!!! 
If by any chance you make a mistake while saving the rule (sometimes the year selection doesn’t stick, so you end up in the scenario described by Bradley), it will silently stop running. 100% agree that the end date should be blank by default.

If this improvement doesn’t qualify as low-hanging fruit, I don’t know what is. Please make this happen!

This got me before (in the days of the “old” advanced JO). Multiple queries, one was set to the current year instead of my then standard “10 years out”.

Y’all -- if I’m launching a recurring program -- I want it to send until I come back and tell it to stop. No, I don’t know when that is. Just keep sending until I say so. This should be an easy admin QoL to add.