## Session Summary (2026-06-17)

- Issue: Cronjob **Rechnungen‑Organizer** failed with `RuntimeError: No LLM provider configured`.
- Resolution steps:
  1. Verified current Hermes config (`hermes config`) – model/provider set to `noris`/`vllm/gpt-oss-120b`.
  2. Updated the cronjob to use the same model/provider via `cronjob action=update`.
  3. Confirmed the job now has `model: vllm/gpt-oss-120b` and `provider: noris`.
- Additional improvement: Added a new pitfall entry to the **cronjob** skill covering the "No LLM provider configured" error and the required `hermes model` / `hermes config set` steps.

**Takeaway:** Always ensure a cronjob’s model/provider aligns with the global Hermes configuration, or explicitly set them on the job.
