Skip to main content
Still200 needs three lifecycle signals from a scheduled job: when it starts, when it finishes successfully, and when it fails. Choose the integration that fits your job.
The Still200 SDK is currently available for Python 3.12 and later. SDKs for more languages are planned. Jobs written in any language can use the HTTP API directly.
The SDK is the quickest way to monitor a Python job. Its @monitor() decorator sends all three lifecycle signals for you while preserving the function’s arguments, return value, and exception behavior.
1

Install the SDK

2

Store the ping token

Copy the ping token generated when you create the monitor and add it to the job’s environment.
Keep the token in your deployment platform’s secret store. Do not commit it to source control or include it directly in the script.
3

Decorate the job

The same decorator works with synchronous functions:
For each invocation, the SDK sends a start ping before calling the function, a finish ping when it returns, or a failure ping when it raises. Failure pings include the exception message, limited to 2,000 characters. Function arguments are never sent automatically because they may contain sensitive data.If a monitoring request fails, the SDK logs the reporting error without changing the job’s behavior: the job still runs, successful return values are preserved, and original exceptions are re-raised.

View on PyPI

SDK source

Start and retry behavior

A start ping is accepted up to 60 seconds before the expected time. A repeated start ping is safe: while a run is already active, Still200 returns that same run instead of creating another one. If a run was already marked missed, a later start may recover that missed occurrence. Its incident resolves after the retried run finishes successfully, and Still200 records the run as late. The finish and fail endpoints return 409 Conflict when the monitor has no running job to complete.
Configure a maximum runtime for every job. It lets Still200 turn a run that starts but never reports finish or fail into a timed_out incident.

Multiple Python jobs

For separate scripts or processes, give each process its own STILL200_PING_TOKEN value:
If multiple monitored jobs run in the same process, load a separate secret for each one and pass it explicitly:
An explicit ping_token takes precedence over STILL200_PING_TOKEN.