Rt.a.utc(...).hour(...).minute(...).local is not a function

[Jiminkim]

hello.

i got this error message and since then,
I can no longer access the query page now.
Can anyone please help me?

I think the cause of the trouble was the wrong specification of the schedule.
When setting the ‘’ Refresh Schedule ‘’ at the bottom left of the query edit screen,
i wrote the schedule time directly, like ‘10: 00’, not using scroll.
i think that was the cause of the error.

but i cant fix the problem because i cant access to the query edit screen because of the error.
how can i solve this problem?

[jesse]

Welcome to the forum and thanks for your bug report!

Your analysis looks correct to me. The query schedule was saved with an invalid time which causes the page to crash.

To Fix

You can fix this pretty easily by running this SQL against Redash’s metadata database:

UPDATE queries SET schedule = null where id =  --QUERY_ID_IN_QUESTION
LIMIT 1

This will remove the schedule so you can access the query and change it.

If you don’t have access to Redash’s metadata database you should ask an admin to do it for you.

Going forward

It shouldn’t be possible to enter an invalid time in the refresh schedule modal. That’s a bug.

You’re running V8 (I think). The good news is I’m not able to reproduce it on V10 (the current release). I’d recommend upgrading to avoid this in the future.

[Jiminkim]

to jesse

UPDATE queries SET schedule = null where id =  --QUERY_ID_IN_QUESTION
LIMIT 1

I appreciate your help.
I will retry this problem.

The good news is I’m not able to reproduce it on V10 (the current release).
I’d recommend upgrading to avoid this in the future.

I understood.
I will suggest it to engineering leader not to make this problem again.