Good point. I think I expose better warnings down stream, but throw them all the way back to the running steps calls, so I can stop them if need be. They stem from the velocity failing more or less, iirc. I can tell steps process stop, something has gone terribly wrong if it gets this far. There are some interdependencies of process that have to go off so other routines don't fail in this case.