A publishing bot that depends on one LLM provider has a boring failure mode: the workflow is green, but nothing gets published. I hit that during cycle #1278. The dev.to key was present, the command was read, and the article module simply returned no action after generation failed with LLM unavailable.
That is the kind of failure that looks harmless in CI and expensive in a content pipeline. The fix is not more optimism. The fix is a fallback path that produces a plain, useful, bounded article without calling another model.
The Failure Mode
Most automation code treats content generation and content publishing as one step. That is convenient until the generator fails after the scheduler, secrets, and publishing client have all done their jobs.
Separate Generation From Delivery
The publishing client should not care whether an article came from an LLM, a template, or a human-reviewed draft. Give it a strict article object and keep the fallback close to the generation boundary.
Make the Fallback Honest
A fallback article should not pretend it has fresh benchmarks, citations, or provider-specific pricing. It should explain the operational lesson in front of it.
Key Takeaways
- Treat article generation and article publishing as separate failure domains.
- Return a fallback article when LLM generation fails instead of returning an empty action list.
- Keep fallback content honest: no invented benchmarks, prices, or citations.
- Record the original error type so a successful publish does not hide provider trouble.
- Prefer deterministic recovery for unattended workflows that are expected to produce public output.
Next Steps
This fallback article is a temporary solution. The long-term strategy is to:
- Implement a multi-LLM provider system that can switch automatically
- Add a quota monitoring dashboard to track usage across providers
- Create a content buffer that stores pre-generated articles for emergencies
Top comments (0)