Dylan Hughes
Dylan Hughes
Requires followup post-redesign
it didn't respect the parameter update: https://cloud.prefect.io/prefect-sales-and-operations/flow-run/fc0f5596-b230-4aca-96a7-8b17dfb49013?overview=
```There was a problem creating your schedule, please try again shortly. Error message: Error: GraphQL error: Invalid clock provided for schedule: {'type': 'CronClock', 'cron': '0 * * * *', 'parameter_defaults':...
+1 to this
For more context: when I encounter an error, I often log a bunch of related information. I want to be able to sift through, reorganize, reformat, copy/paste, and share these...
Also for the record, the "download the logs displayed on this page" without a "download all of the logs" can be pretty frustrating. I can see myself holding CMD+⬇️ after...
The Cloud compatibility test should resolve after the next Cloud release
> maybe we could add a test for the deprecation warning case? and just out of curiosity, why FutureWarning instead of DeprecationWarning? @zzstoatzz I will add a test for the...
Thanks for that @DataOps7 and @barskern -- would you mind sharing the schedules for the deployments you're seeing issues for? I'm having trouble recreating this bug (even offline)