diditarrive
Sign inSign up

Use case

It is coming sometime this week, and the arrival is the news.

An auditor, a vendor re-send, the first file of a migration. There is no schedule, only a deadline, and the alternative is a calendar reminder to go and look.

How it fails today

Somebody remembers to check on Tuesday and Thursday, and not on Wednesday, which is the day it landed. Or it never lands, and that is discovered the following week.

The deadline passes, and nothing anywhere says so.

What we do about it

The week, as we would run it
  1. when you saveThe window opens immediately. Early is the point, not a problem.
  2. Thursday 09:12It arrives. One alert, 32 hours before the deadline.
  3. after thatFinished. The watch is over and stays quiet forever.

What we need

The same connection a recurring monitor uses. What changes is that it has a deadline instead of a schedule, and a rough deadline is fine. The full posture.

a deadline, not a scheduleat most two alertsfinishes by itself
The monitor, configured

Auditor's year-end pack

Where
SFTP, /inbound
Deadline
Friday 17:00 EST
Tell you
the moment it arrives, or if the deadline passes

If the key expires, that’s Check broken, never Missed - broken access is its own alert, and it says whose job it is to fix.

Set it up in a sentence:

“The auditor's pack should land in /inbound sometime this week, tell me the moment it does.”

Create monitor
Same shape, different plumbing:The connectorsThe schedule modelPricing
Menu
ProductUse CasesConnectorsPricingTrustSign inSign up