This message was deleted.

There doesn't seem to be a specific open issue related to your described problem with Prefect UI deployment schedule parameter overrides passing a dictionary instead of the expected parameter type. However, issues with parameter handling and serialization have been noted in other contexts, such as handling

None

values and parameter validation. Given the nature of your problem, it might be related to how Prefect serializes parameters for scheduled runs. You might want to check how parameters are being serialized and deserialized in your deployment setup, especially focusing on whether the UI is correctly interpreting the parameter types. For now, I recommend reaching out to the Prefect community or opening a new issue on their GitHub repository with detailed information about your deployment configuration and the problem you're encountering. If you can, include any relevant logs or error messages to help diagnose the issue. For further exploration, you can visit the Prefect GitHub issues page here.