This is very interesting. Currently we don’t want to stop data, event if it is dirty. We do add error message instead inside the data so that downstream process could decide.
However, that means dirty data can come through and make downstreams dirty.
We might need to consider this design decision sometime in the future, whether it’s better to give data user two choice only 1) data exist and correct 2) data is not exist and incorrect