Two quick options to explore - you might find combing them helps. Firstly, the Verification tab lets you stop a process if a filtered set of the table has fewer than n rows.
If your process generates output burst on all filters, then you might need to split the file creation and file distribution into separate projects. The first one could create all the files, then the second one could open each file, and apply a model to test whether there's data, and apply an input distribution if the file isn't empty.
Hope this helps,
Thanks, Olly! I understand both solutions, I believe, and will take a look at the best method for this particular set of reports. It would seem elegant to have that same kind of logic on the Export side as well. After the file is read in, "If this summary (filter) has no results, then don't run the export". A guy can dream!