Runtime not recovering after function loader is reset as a result of a failed compilation

If there is a compiler failure, the compilation results are not cached and the function loader is reset. This should allow the runtime to trigger compilation on subsequent executions, but in the startup path, the HTTP function is not loaded/registered, so execution (therefore, compilation) is never attempted.