Report marked failed if empty set

[lucienorrin]

Why are reports that return zero values marked as failed?

We have several reports that can often not have any data returned. No data does not equal a failed report.

1. The task executions page shows the reports as failed.

    The task did actually send out an email so I don't think it failed.

    This should not be marked as failed, warning maybe. "Complete with exceptions" perhaps?

2. An email was actually sent to the recipients with a confusing error. Blacked out personal info.

I agree the task may have failed to return any data, but that doesn't mean the report failed. It just means the queries and filters didn't return any data.

Knowing there were zero results returned for a specified time can be just as, or more important than, knowing the actual data.

This doesn't differentiate between an actual failed report and an empty set.

Users will contact us reporting failures when there were just zero matches.

3. There is a misspelling in the error message: "wiht"

Is there any way to customize the failed to generate error message?

And specify a separate message specifically for "empty set" failures?

[Daniel_Jenkins]

Hi Lucien,

Thanks for the feedback. There is already quite a bit of internal discussion going on about this. I have passed on your views to Product Management. I hear that changes are being formulated in this area but have no information on exactly "what" & "when".

Best - Daniel.

[lucienorrin]

Thanks for passing it along.

Glad to hear it is being talked about.