As I continue to learn how to develop blueprints, I’m looking for tips on best practices on how to debug. It is pretty straight forward to yaml-lint validate, and once it is running the trace tool is amazing.
But often I have a typo/syntax error that gets identified in " Settings > Automations > Blueprints" where it will say Invalid blueprint: {error message} – but the {error message} is typically cut off in the UI. Is there somewhere else where I can see the entire message of what is wrong?
If you are editing with VSCode, it will often pop an error message in the bottom right of the screen when you use the command pallet to restart the automation or script, depending on the BP type.
Also if you are still in the visual editor of the automation/script that calls the BP, the error will be on the top of the screen when you try to run it from the menu and it will quick flash on the bottom of the screen.
Other than that Using VSCode tied to a GIT repo, you can see what changes were made and it makes it easier to see what you changed to pick out the missing curly brace out of the 700 lines of YAML, as happens to me often…
Thanks. I managed to figure out my specific problem, though when the error is in the blueprint section that means you can’t launch the blueprint UI at all, and that cropped error is the only clue as to why it is invalid. I have seen the top line error you mentioned on automatons and the git compare is a good tip, thank you!