Email notifications
Every email Runjet sends — when it arrives, to whom, and what it will not do. One section per template, no more and no fewer.
Runjet sends thirteen kinds of message and all of them are here. They fall into three families by who receives them: about your account to you, about operations to everyone who administers or operates the workspace, and about the workspace itself to the billing address.
Who gets what
| Family | Recipient |
|---|---|
| account | the one person whose account it concerns |
| operations | every account with the admin or operator role (roles) |
| workspace | the billing address — the one the workspace has had since registration |
Operations messages can be switched off per job with the switch on the job form; messages about agents and about the workspace cannot be switched off.
About your account
Confirming a registration
"Somebody asked for a Runjet workspace called … using this address. Confirm it and choose a password." It arrives after the registration form is submitted; the link lasts 48 hours and only it creates the workspace (registration).
An invitation
"X has given you access to Runjet as role. Choose a password to get in." The link lasts seven days and works once; a new one replaces the old (invitations).
A password reset
"Somebody asked to reset the password for … If that was you, type this code into the page that asked for it", and a six-digit code. Deliberately without a button. It lasts ten minutes (a forgotten password).
About operations
A job failed
"X failed on agent", with the exit status and the verdict's sentence. It arrives once, when the job starts failing on that agent, and then no more: "a job that keeps failing does not keep writing to you". A run killed by an agent shutting down counts as a failure too — from Runjet there is no telling why the agent went down, and most of the reasons are not your doing.
A job is working again
"X is working again on agent." The second half of the previous message; it arrives after the first success following a reported failure, and at no other time.
A run is taking a long time
"X has been running on agent for …, which is past the … you asked to hear about. It is still going. Runjet has not stopped it and will not." Once per run, never twice; the threshold is per job, eight hours by default (long-running jobs). It stops nothing.
An agent has stopped checking in
"X has stopped checking in. It was last heard from … N jobs are pointed at it, and they will not run until it is back." After ten minutes of silence, once per outage; the agent's return resets the counter. Only for agents that jobs are aimed at. What to do about it is in troubleshooting.
About the workspace
Your contract and Terms of Service
"This confirms the contract: attached are the Terms of Service you agreed to, version …, in Czech and in English. The Czech text prevails." With the Terms as two PDF attachments. Once when your workspace is ready after registration, carrying the version you accepted there, and once for each subscription you buy, carrying the Terms in force at that purchase and naming the plan. Keep it: the Terms that apply to you are the ones attached, whatever runjet.dev shows later.
The free month is ending
"The free month for X ends in N days. After that your jobs stop being scheduled — everything stays readable, and nothing is deleted." Five days and two days before the end, if the workspace is not paying yet (the workspace's life).
A payment did not go through
"A payment for X did not go through. Your jobs are still running. The card will be tried again over the next couple of weeks." Nothing stops; the payment provider retries the card. Once per failed payment.
Scheduling has stopped
"Scheduling has stopped for X. Your jobs, agents and run history are all still there and still readable — they are simply not running. … the workspace is deleted in 30 days." When the free month ends without a payment, or a subscription ends (suspension).
Deletion is approaching
"X will be deleted in N days. Subscribing before then brings it straight back … you can export it while it is still readable." Fifteen, five and two days before deletion, counted from the suspension. Export works for the whole of that time.
Deleted
"X has been deleted. Its address no longer resolves and its agents can no longer reach it. The data is held for another 30 days. If this was a mistake, reply to this message within that time." After thirty days of suspension (deletion).
What an email is not
None of these messages does anything. A failed job is not switched off, a long run is not stopped, an offline agent is not deleted. The email is what you find out; what to do about it is always yours, on the screen it links to.