Disclaimer: we might have spoken about this before but I don't remember. It's not documented in any GitHub issue as far as I could see. I don't know if there are technical reasons behind this or if it's just something that we haven't got right yet.
Steps to reproduce
Start a GoGoDuck aggregation where the geographic boundary will not cover any data
(NB. The time range needs to be small enough that there aren't more files than GoGoDuck's configured limit)
What does happen
Both the status page and email acknowledge there was an error but give no more information (see below)
The report does not have any indication that there was an error or what it might have been (see below)
What should happen
We should indicate what the problem was (ie. no data matched the subset criteria) either in the status page/email or in the report (or both)
More info
The status page message
Reason: Internal error running GoGoDuck, please refer to report for more information
The email message
...
Something has gone wrong with your download request. Please see the attached log for more details:
...
Disclaimer: we might have spoken about this before but I don't remember. It's not documented in any GitHub issue as far as I could see. I don't know if there are technical reasons behind this or if it's just something that we haven't got right yet.
Steps to reproduce
(NB. The time range needs to be small enough that there aren't more files than GoGoDuck's configured limit)
What does happen
What should happen
More info
The status page message
The email message
The report
ie. There is nothing to indicate that anything went wrong