<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Error Handling on Rob Sewell (aka SQL DBA With A Beard)</title><link>https://blog.robsewell.com/tags/error-handling/</link><description>Recent content in Error Handling on Rob Sewell (aka SQL DBA With A Beard)</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 10 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.robsewell.com/tags/error-handling/index.xml" rel="self" type="application/rss+xml"/><item><title>MicrosoftFabricMgmt: Error Handling - Retry Logic and Long Running Operations</title><link>https://blog.robsewell.com/blog/microsoftfabricmgmt-error-handling/</link><pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate><guid>https://blog.robsewell.com/blog/microsoftfabricmgmt-error-handling/</guid><description>&lt;img src="https://blog.robsewell.com/assets/uploads/2026/03/lro.png" alt="Featured image of post MicrosoftFabricMgmt: Error Handling - Retry Logic and Long Running Operations" /&gt;&lt;h2 id="introduction"&gt;Introduction
&lt;/h2&gt;&lt;p&gt;REST APIs fail. Networks are unreliable. Cloud services have rate limits. If your automation script does not account for this, it will eventually break at the worst possible moment. This is not pessimism — it is production experience.&lt;/p&gt;
&lt;p&gt;MicrosoftFabricMgmt has a lot of error handling built in, so you do not have to write it all yourself. Today I want to show you what the module handles automatically, and how to add your own handling on top for the scenarios you care about.&lt;/p&gt;</description></item></channel></rss>