Skip to content
EyeOnTask Knowledge Base

Today's Recurring Report

Recurring work is the work nobody watches. A recurring job or a recurring invoice is set up once and then expected to appear on its own, week after week, without anybody opening it.

Which is exactly why it fails quietly. Today’s Recurring Report is the check: of everything due to be generated today, what was, and what was not.

Open it from Add Report — see generating a report.

What it asks for

Section titled “What it asks for”

Nothing. The report covers today, so there is no date range to set and no filter to choose. Generate Report runs it.

The three options above the button decide whether the result is emailed as well as shown:

  • Don’t Send Email — show it on screen only.
  • Send Regular Email — send it whatever it says.
  • Send Email Only in case of failure — send it only when something did not generate.

The third is the one to use on a saved and scheduled copy of this report. A report that arrives every morning saying everything is fine is a report people stop opening; one that only arrives when something broke is one they read.

What comes back

Section titled “What comes back”

Summary is the whole health check in six numbers — one row for Job, one for Invoice, and three figures against each:

  • Scheduled — how many were due to be generated today.
  • Created — how many actually were.
  • Failed — how many did not.

Scheduled and Created matching, with Failed at zero, is the answer you want.

Underneath, Job Details and Invoice Details name the individual ones: the Parent Job or Parent Invoice the recurrence is set on, the Created Child it produced, the Client Name, and the Status.

When something failed

Section titled “When something failed”

The parent is where you go. A recurrence generates from its parent’s settings, so a failure is almost always something on the parent that is no longer true — the client or site it points at, the items or rates on it, or the schedule itself having run past its end date.

Open the parent named in the row and check it against a child that generated successfully. For how the schedule itself is set and stopped, see recurring jobs and, for invoices, how recurring patterns work.

Contract-driven billing recurs from the contract rather than from an invoice — see contract invoicing.

Section titled “Related”