> For the complete documentation index, see [llms.txt](https://docs.layerlens.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.layerlens.ai/9.-improve-tune-the-system/daily-smoke-eval.md).

# Daily smoke eval

Run a small (≤50 trace) evaluation daily. Goal: detect "did anything break overnight" — model provider drift, prompt regression, infra issues.

The SDK doesn't ship a scheduler. Wire the SDK call into your existing scheduler (cron, GitHub Actions schedule, Lambda EventBridge, k8s CronJob).

## SDK call (run from your scheduler)

```python
from layerlens import Stratix
client = Stratix()

# Pull recent representative traces
traces = client.traces.get_many(page=1, page_size=50, sort_by="created_at", sort_order="desc")

# Evaluate each with your smoke-test judge
import asyncio
from layerlens import AsyncStratix
async def smoke():
 aclient = AsyncStratix()
 creates = [aclient.trace_evaluations.create(trace_id=t.id, judge_id=SMOKE_JUDGE_ID) for t in traces.traces]
 evals = await asyncio.gather(*creates)
 return await asyncio.gather(*[aclient.trace_evaluations.wait_for_completion(e.id) for e in evals])

results = asyncio.run(smoke())
failed = [r for r in results if not r.passed]
if failed:
 raise SystemExit(f"Smoke eval failed: {len(failed)} of {len(results)}")
```

## Wire to a scheduler

GitHub Actions:

```yaml
on:
 schedule:
 - cron: "0 7 * * *" # 07:00 UTC daily
jobs:
 smoke:
 runs-on: ubuntu-latest
 steps:
 - run: python scripts/smoke_eval.py
 env:
 LAYERLENS_STRATIX_API_KEY: ${{ secrets.LAYERLENS_STRATIX_API_KEY }}
```

Or Linux cron, k8s CronJob, etc.

## See also

* [Concept: Continuous evaluation](/7.-observe-see-whats-happening/continuous-evaluation.md)
* [Cookbook: containerized CI](/6.-build-wire-your-code/containerized-ci.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.layerlens.ai/9.-improve-tune-the-system/daily-smoke-eval.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.