Summary
The user faced a FlyteInvalidInputException while registering a workflow with FlyteRemote using flytekit versions above 1.11, despite all tasks being registered. They identified the issue as a mismatch in serialization_settings due to unspecified domain and project. The user speculated that recent changes in the FlyteRemote API might have contributed to this problem and noted that these parameters need to be explicitly passed to remote.register_workflow() through the serialization_settings argument, in addition to being specified during FlyteRemote instantiation.