@Marvin Why is Prefect Cloud specifying the following flow parameters:

{
  "value": "{}",
  "__prefect_kind": "json"
}

when I didn't declare these anywhere?

The presence of the

__prefect_kind

attribute in your flow parameters, specifically set to

"json"

, seems to be related to how Prefect Cloud handles parameter serialization and display in its UI. There was a recent update in the Prefect UI library that added support for this kind of schema handling, as noted in a GitHub issue and related pull requests. This attribute might be automatically added by Prefect Cloud to ensure that parameters are correctly serialized and deserialized as JSON. It could also be a result of changes in how the Prefect UI displays parameters, where it now defaults to showing them in a JSON format. If you haven't explicitly set these parameters, they might be part of the internal handling by Prefect Cloud to maintain consistency and compatibility with their UI and API. If this behavior is causing issues or confusion, you might want to check any recent changes in the Prefect Cloud version you are using or raise a query with their support. For more detailed information, you can explore the Prefect documentation or review the related GitHub discussions.

@Marvin when I update the schedule in Prefect Cloud UI, it always adds the prefect kind , How can I set the parameters to be completely empty

The Prefect documentation does not explicitly mention how to remove the

__prefect_kind

attribute or how to set parameters to be completely empty when updating a schedule in the Prefect Cloud UI. It seems that this attribute is automatically managed by Prefect to handle parameter serialization. However, you can try the following general approach to ensure parameters are empty: 1. Check the UI Configuration: When updating the schedule, ensure that no parameters are being inadvertently added. Sometimes default parameters might be set automatically, so clear any fields in the UI that might contain default values. 2. Use the Prefect API: If the UI does not allow you to set parameters to be empty, consider using the Prefect API to update your schedule programmatically. This might give you more control over the parameters being set. 3. Inspect Defaults: Check if there are any default settings in your Prefect configuration that might be adding these parameters. This can be done through the Prefect configuration settings. If these steps do not resolve the issue, it might be beneficial to reach out to Prefect support or check their community forums for more specific guidance tailored to your version and setup. You can also explore more about scheduling in Prefect Cloud here.