A projected run has not delivered anything.
Separate the timing question from whether your own task executes, publishes a usable page or sends a readable email.
One small trial
Use an identifiable, nonsensitive test.
Choose a one-shot in your actual Hermes environment and give its output a unique marker, such as schedule-trial-2026-10-15-A. Use your existing task, gateway and delivery configuration. MinuteField neither connects to that installation nor creates the job.
- Check the executable schedule string and timezone in the real task.
- Note its stored next-run time before waiting.
- Keep the gateway available during the trial.
- Afterward, inspect the actual run record, then the separate destination.
- Compare the unique marker and timestamps. Record failures without treating a missing message as proof that the timing expression was wrong.
A real task may involve your existing provider or integration costs. The calendar itself uses no model API and does not start that work. A successful synthetic trial supports only the behavior you actually observed.
If the job publishes a page
Check the output as a new visitor.
For a scheduled task that updates a public page you own, an already-signed-in browser can hide access or stale-session problems. Open the public result in a fresh browser profile and check the marker, readable content and intended public URL.
WebTraceCheck is an optional way to carry out that fresh-browser check. You can also use your own separate test profile. It does not confirm that the scheduler ran at the expected time; the run record and the visible page answer different questions.
Useful observation: “The run record says success at 09:02; a fresh visitor sees marker A on the intended page at 09:04.” Avoid upgrading that into “all future runs are reliable” or “every viewer gets the same result.”
If the job sends email
Inspect a disposable delivery, not an account recovery flow.
If your own task already sends email through a configured sender, you may use CleanTempMail as a temporary destination for a nonsensitive test message. Confirm that your sender accepts the address, then inspect the subject, marker, body and any links that matter to this test.
Do not use a public temporary mailbox for a Hermes account, credentials, private logs, personal data or important recovery. If the test needs sensitive information, use a private test inbox you control. A temporary address may expire or be rejected by a sender, so check availability before the scheduled trial.
Receiving one message does not establish inbox placement, future deliverability or scheduler accuracy. If nothing arrives, inspect the sending step, destination and timing evidence separately. This site has not sent an email on your behalf.
Keep a useful note
Four observations are more useful than one green badge.
| Observation | Where it comes from |
|---|---|
| Intended schedule and zone | Your authored input and real task settings |
| Stored next run | Your Hermes installation |
| Actual completion and status | The real run record |
| Visible page or received message | The actual destination |
MinuteField’s saved JSON contains rehearsal settings only. It is not an execution receipt, not a deployment artifact and not an importable Hermes job. Keep real observation notes separately.
WebTraceCheck and CleanTempMail are operated by the same operator as MinuteField. Links carry site and placement campaign labels, never your schedule input. Both services are optional; their own policies apply.