I don't know what the "Con-call" error is.
There's no out of the box way to do this, but it is possible. Here's my suggestion:
First, update all of your function recipes with a new boolean input parameter called something like "test". Add actions into each recipe so when it is called and test is true, the recipe stops immediately. This will allow you to call the recipe to check if it is on without having to run the entire recipe.
Second, make a new pre-flight verifier recipe where you call each function with "test" set to true. Each function should be within an error handler, and on error you should add the recipe name to a list and proceed with calling the next recipe to test. If any recipe is off, its name will get added to the list. Repeat this step for as many functions as you want to test.
At the end of the recipe, if the list exists (meaning some recipes are inactive) you can do whatever you need to do with the list of inactive recipes. Throw an error, email the list, whatever you want. If the list if empty, this means all of your recipes are on and you're ok to proceed with your workflow.
Lastly, make sure to call the pre-flight verifier recipe from an appropriate location in your workflow.
