<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Retries on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/retries/</link><description>Recent content in Retries on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/retries/index.xml" rel="self" type="application/rss+xml"/><item><title>Mastering Basic Workflows: Events, Tasks, and Retries</title><link>https://ai-blog.noorshomelab.dev/triggerdev-v4-guide-2026/basic-workflows-events-tasks-retries/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/triggerdev-v4-guide-2026/basic-workflows-events-tasks-retries/</guid><description>&lt;p&gt;Welcome back! In the previous chapter, we successfully set up our Trigger.dev project, getting ready to build powerful automated systems. Now, it&amp;rsquo;s time to dive into the fundamental building blocks that make Trigger.dev workflows so resilient and effective: &lt;strong&gt;Events&lt;/strong&gt;, &lt;strong&gt;Tasks&lt;/strong&gt;, and &lt;strong&gt;Retries&lt;/strong&gt;. These three concepts are the bedrock for creating robust, automated workflows and AI agents that gracefully handle the complexities and inevitable failures of real-world production environments.&lt;/p&gt;
&lt;p&gt;This chapter will guide you through understanding what events are, how tasks execute reliably, and how Trigger.dev automatically handles failures through intelligent retries. By the end, you&amp;rsquo;ll be able to create your first resilient workflow, capable of reacting to external signals and executing durable, fault-tolerant operations, boosting your confidence in building production-ready systems.&lt;/p&gt;</description></item><item><title>Building Resilient Systems: Retries, Timeouts, and Circuit Breakers</title><link>https://ai-blog.noorshomelab.dev/systems-engineering-2026/resilience-patterns/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/systems-engineering-2026/resilience-patterns/</guid><description>&lt;p&gt;Distributed systems are powerful, allowing us to scale applications and handle immense loads by breaking them into smaller, interconnected services. But here&amp;rsquo;s a secret: they &lt;em&gt;will&lt;/em&gt; fail. Networks are unreliable, services can crash, and dependencies can slow down. The real challenge isn&amp;rsquo;t preventing all failures (an impossible task), but designing systems that can &lt;em&gt;tolerate&lt;/em&gt; failures and continue to function gracefully.&lt;/p&gt;
&lt;p&gt;This chapter dives into three fundamental patterns that form the bedrock of resilient distributed systems: &lt;strong&gt;Retries&lt;/strong&gt;, &lt;strong&gt;Timeouts&lt;/strong&gt;, and &lt;strong&gt;Circuit Breakers&lt;/strong&gt;. You&amp;rsquo;ll learn what each pattern is, why it&amp;rsquo;s crucial, and how to apply it effectively to build applications that can withstand the chaos of a distributed environment. We&amp;rsquo;ll also explore how these timeless principles are vital for emerging AI and agentic workflows, where interactions with external tools and models are frequent and often unpredictable.&lt;/p&gt;</description></item><item><title>Chapter 11: Error Handling, Robustness, and Retries</title><link>https://ai-blog.noorshomelab.dev/langextract-guide-2026/11-error-handling/</link><pubDate>Mon, 05 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/langextract-guide-2026/11-error-handling/</guid><description>&lt;h2 id="chapter-11-error-handling-robustness-and-retries"&gt;Chapter 11: Error Handling, Robustness, and Retries&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid data explorer! So far, we&amp;rsquo;ve learned how to set up LangExtract, define schemas, and perform extractions with various LLM providers. You&amp;rsquo;re getting good at asking LLMs to do your bidding!&lt;/p&gt;
&lt;p&gt;But here&amp;rsquo;s a little secret: even the smartest LLMs and the most robust libraries aren&amp;rsquo;t perfect. In the real world, things can go wrong. Network glitches, API rate limits, unexpected model behavior, or even a moment of LLM &amp;ldquo;confusion&amp;rdquo; can lead to failed extractions or malformed output. If we&amp;rsquo;re building applications that rely on these extractions, we need them to be as reliable as possible.&lt;/p&gt;</description></item></channel></rss>