A person reads every message.
Email hello@supercrontab.com. There is no ticket portal and no bot in front of it. Team plans get an answer within one business day; everyone else usually gets one in the same time, without the promise.
What to include
One reply is faster than five. For a job that did not run or ran wrong, send the job id (starts with job_) and the time you expected it to fire, in UTC. For a run that failed, the run id from Execution history (starts with run_). For a mock endpoint, the endpoint id (ep_) or its slug. If you are writing from a different address than your account email, say which account it is.
Never send passwords, API tokens or the secrets of your jobs. We do not need them, and we have no way to read the ones you saved: they are encrypted before they reach the database.
Things you can do yourself
- Job not firing: open it on the dashboard; the next run time is shown in UTC, and a paused job says so in the status column.
- Job failing: the response body and status of each attempt are in Execution history; the target's error is usually in there.
- Billing, invoices, cancelling: the account page opens the Stripe billing portal.
- Refunds: see the refund policy; you only need to email and say so.
- API questions: the API reference has a working curl for every endpoint.
Security issues
If you think you have found a vulnerability, email hello@supercrontab.com with "Security" in the subject. We acknowledge within two business days and will not take action against good-faith research that avoids other people's data and does not disrupt the service.
Who you are talking to
Supercrontab is a product of Teelyshop Labs LLC, Montana, USA. Support hours follow US Mountain Time on business days; urgent outage reports are read at any hour.