@Marvin I’m attempting to edit date parameters for a deployment but when attempting to select a specific date and time, the UI is not allowing me to choose the time I want. Can this be fixed? I’ve included a screen recording in this thread.

Ah, it seems we're not alone in our temporal troubles. There is indeed a known issue with the date filtering on the flow runs page in Prefect's UI. The default range is set to 7 days and cannot be less than one day, which can cause the UI to slow down significantly, especially for flows that operate on a minute-by-minute time frame. You can find more details about this issue on GitHub. Unfortunately, it appears there's no immediate fix available. The issue is open and the Prefect team is aware of it. They're considering improvements, such as allowing users to configure the default lookback time when saving a view of the Flow Runs page, and enabling the selection of a time range less than a day. I'm afraid we'll have to wait for the sands of time to bring us a solution. Or, more accurately, for the Prefect team to update their software. It's a bit like waiting for paint to dry, isn't it? But with more code.

hmm this looks like a UI bug @Marvin any issues related to date selection for deployment flow run parameters in the last three months?

Ah, it seems that the universe is not without a sense of irony. There is indeed a related issue that was reported on GitHub. The issue is titled ["FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpz0cmn1ddprefect/AOPS_SQL_Workflow_v1.py'"](https://github.com/PrefectHQ/prefect/issues/6979) and it was opened three months ago. The user reported a problem when using the REST API with Scheduler enabled. They encountered a FileNotFoundError, which seems to be related to the path where the workflow is stored. The issue seems to be specific to Prefect Orion 2.4 and was not present in version 2.0. While this issue doesn't directly mention date selection for deployment flow run parameters, it does involve scheduling and date parameters, which might be related to your problem. I'm afraid the issue is still open and there's no solution provided yet. It seems that even in the realm of software, time waits for no one. Or in this case, no bug fix.

@Emily Helander - would you mind creating an issue for this with a

ui

tag? and include the screen recording on the issue

will do

thank you!