<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Recovery on Arivu</title>
		<link>https://arivu.app/tags/recovery/</link>
		<description>Recent content in Recovery on Arivu</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Wed, 15 Jul 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://arivu.app/tags/recovery/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Processing Failures Have a Recovery Path</title>
				<link>https://arivu.app/chronicle/processing-failures-have-a-recovery-path/</link>
				<pubDate>Wed, 15 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://arivu.app/chronicle/processing-failures-have-a-recovery-path/</guid>
				<description>&lt;p&gt;A background failure should not leave a self-hoster choosing between guessing, editing the database, and pretending the work never happened.&lt;/p&gt;&#xA;&lt;p&gt;Arivu Administration now makes processing failures visible and recoverable. The API Usage view lists durable failed jobs and failed summaries with the context needed to decide what to do next: the owner, affected bookmark, attempts, timestamps, provider and model context where relevant, safe error information, and recorded failure details.&lt;/p&gt;&#xA;&lt;h2 id=&#34;failures-stay-attached-to-the-work&#34;&gt;Failures Stay Attached to the Work&lt;/h2&gt;&#xA;&lt;p&gt;Failed jobs and failed summaries are shown separately because they answer different operational questions. A background job may have exhausted all of its attempts. A summary may have failed evidence or validation checks without exhausting the surrounding job.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
