<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Long-Running Jobs on FlowChassis.com</title>
    <link>https://flowchassis.com/tags/long-running-jobs/</link>
    <description>Recent content in Long-Running Jobs on FlowChassis.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://flowchassis.com/tags/long-running-jobs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Video Transcoding With FlowChassis Survives a Crash Without Starting Over</title>
      <link>https://flowchassis.com/video-transcoding-with-flowchassis-survives-a-crash-without-starting-over/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://flowchassis.com/video-transcoding-with-flowchassis-survives-a-crash-without-starting-over/</guid>
      <description>&lt;p&gt;Some jobs take minutes or hours. Transcoding a long video is the classic one. The usual design is a worker that picks up the job and grinds through it, and when that worker dies at 80 percent, say because a deploy restarted it, the job starts again from zero.&lt;/p&gt;&#xA;&lt;p&gt;Starting over is fine once. On a busy system with regular deploys it means the longest jobs are the ones that never finish.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
