Is this expected or a bug: I'm getting `Invalid cr...
# ask-community
c
Is this expected or a bug: I'm getting
Invalid cron string EDT
for a schedule when I set it to
@daily
with
execution_timezone=US/Eastern
I'd expect it to run at midnight for the timezone specified, but does it only support UTC?
d
definitely sounds like a bug - do you have a full stack trace?
c
no exception actually, it just shows up on the schedule screen
this is on Dagster Cloud for context
k8s agent
d
Ah I think this is confusing copy. It's not saying EDT is the problem, it's saying it can't parse the cronstring (it's two separate lines)
What's the schedule cron string?
oh its just @daily?
c
yeah it's daily
d
My guess is that this is a frontend bug and the schedule will actually work fine, but I will confirm that.
c
yup if I turn it on, it looks like it understands the cron string
just the display is messed up
d
Roger - we'll get a fix out for that, thanks for the report
d
Fix is merged, you’ll see it in the next release 🙂