Parsing error at DFDL , it's not throwing the correct error message

RFE Review. Thank you for taking the time to raise this RFE and apologies it has been in submitted status for so long. For the benefit of other readers who may potentially wish to vote for this enhancement request, the position which is outlined in more detail in your salesforce case relates to a DFDL model which had an unbounded number of DetailRecord blocks after an initial header. There was no initiator or terminator to indicate when the DetailRecords are finished. For this reason the DFDL parser is adopting a position of assuming all the data belongs to a block until it finds a problem. When it finds that problem, it signals the end of the block and then attempts to parse the data in a different way against the model. Ultimately it then attempts resolution using the FileTrailer block. In these situations, you expressed frustration that the DFDL error of most value to the developer was somewhat hard to find within the wider DFDL commentary around how it was backtracking and attempting different options against your model. We interpret that this RFE is designed to ask for the incremental "potential" errors, which are visible in the DFDL Test perspective of the Toolkit to also be logged by the runtime, perhaps optionally via a configuration of some form, to aid problem diagnosis. We think this sounds like a good idea, but potentially with value to a small subset of users. We will continue to monitor this RFE for popularity. Meanwhile status is updated to Uncommitted Candidate.