cronmiss
Know when a scheduled job did not run.
Your job pings cronmiss when it finishes. If the ping is late or missing, you get an alert. That catches the failure that leaves no error behind: the cron that simply never fired.
Early release. The cronmiss service is not open for sign-ups yet; this client is published ahead of it. See cronmiss.com.
from cronmiss import ping, monitor
# At the end of a job
ping("YOUR-MONITOR-ID")
# Or decorate the job: start, then success, or fail with the error message
@monitor("YOUR-MONITOR-ID")
def sync_invoices():
...
ping never raises and returns True when the ping was recorded. Monitoring should never be the reason a job fails. Standard library only.
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for cronmiss 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cronmiss-0.0.1.tar.gz | 3.6 kB | Without provenance | Details for cronmiss-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cronmiss-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for cronmiss-0.0.1-py3-none-any.whl |
Total release size: 7.5 kB
Release files / cronmiss-0.0.1.tar.gz
| Download URL | cronmiss-0.0.1.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bfa2baa4317d149ae84d619d191744f18963b3c84c740423aed5995aec5f398b
|
|
BLAKE2b-256 checksum How to use checksums |
d936e71645f08004447aa3e71f4f1771b16ce2ec2ae839e38e1e0688756324c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.14.4
|
Release files / cronmiss-0.0.1-py3-none-any.whl
| Download URL | cronmiss-0.0.1-py3-none-any.whl |
|---|---|
| Size | 3.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c183fd4a169ac99f59e6b95650cccb4a1d0188c9fbf7265bdd20b65f4d9cae33
|
|
BLAKE2b-256 checksum How to use checksums |
cdb354e670142238316a0015732153061b8d04a2ebc4e9207480d1171a3c80c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.14.4
|
Security for cronmiss 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
