We ran into this error when updating a project into the automation node:
It took us some time to figure out what was happening:
It would have been helpful to point out further details on this error to help the user understand what was happening. Overall, there seems to be room for improvement for the management of warnings & errors when deploying a project to Automation (e.g. warnings that are not necessarily relevant to the user).
cc @tgb417, @Turribeach