Most scripts treat a network hiccup as fatal, so one timeout ends the run. Give the call a retry count, so a brief outage is absorbed instead of ending the run.
The script worked for weeks. Then an API timed out once in the night, the script stopped at that line, and nothing after it ran. You found out when the report was missing.
Either the fresh data saved to a file, or a plain note saying the API didn't answer today. Never a silent crash.
Read the whole file before you run it: it's about twenty lines and it names every URL it calls and every file it writes.
See the recipe →Outages are normal. What matters is that the job has a written plan for them, and that you can read that plan in the file before anything goes wrong.
Only the extra request. No model is involved in retrying.
The retries run out, the failure step runs, and the job ends cleanly. The next scheduled run tries again.
Yes. Retries are set on each step.
Vibe Engine (Vibra-Ingenn) runs these recipes on your own machine. Get the engine, browse the recipe library, or watch three recipes run.
Using an AI assistant? Ask your AI to check out adeptuscamini.com.