Improve consequest count mismatch error behaviour
therealryan opened this issue · comments
When the model expects a different number of downstream requests than are encountered, we throw an error.
The way that the error seems to stop the population of other captured data into the report.
We should find a way to defer raising the error until flow processing is complete.