Currently the Notification message created by the ImportServiceImpl class contains the value found in the tag as the published-min query value. In the case of uploaded IntervalBlock entries, the tag contains the date representing the end of the IntervalBlock, NOT the start of the IntervalBlock. Therefore, using the IntervalBlock tag causes OpenESPI to "skip" the IntervalBlocks with values earlier than the IntervalBlock tag
Upon investigation, the issue is a by product of modifying the ExportFilter class to extract IntervalBlock data by inspecting the IntervalBlock start time rather than using the Atom tag, as originally designed. The change was made to accommodate a Data Custodian Connect My Data certification test harness revision required to enable the CMD certification test beta test partners to pass [FB_37] Query Parameters.