When a recipe application fails, usually due to a config validation error, the error message that is displayed is unrelated to the actual issue, like text formats or editor plugins.
@phenaproxima pointed out on Slack:
Normally, when that happens, the recipe runner tries to roll back the changes - this is done using the config importer. The problem is that the config importer is also failing, and you’re only seeing that error, not the original error that triggered the rollback. It’s a flaw in the drupal recipe command.
TBD
Improve the clarity of the command, but also fix the underlying core bug which causes that specific rollback error.
Active
11.0 🔥
recipe system
It turns out that we already do what this issue asks for, and indeed have test coverage of that, in \Drupal\FunctionalTests\Core\Recipe\RecipeCommandTest::testExceptionOnRollback().
So maybe we should repurpose this issue to fix one of the underlying issues that can cause a rollback in the first place?