<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Serverless on Codeslog</title>
    <link>https://www.codeslog.com/en/tags/serverless/</link>
    <description>Recent content in Serverless on Codeslog</description>
    <image>
      <title>Codeslog</title>
      <url>https://www.codeslog.com/images/default-cover.png?v=20260114T1436</url>
      <link>https://www.codeslog.com/images/default-cover.png?v=20260114T1436</link>
    </image>
    <generator>Hugo -- 0.150.0</generator>
    <language>en-US</language>
    <lastBuildDate>Fri, 24 Jul 2026 01:45:00 +0900</lastBuildDate>
    <atom:link href="https://www.codeslog.com/en/tags/serverless/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Zombie Task Stuck in &#39;Scanning&#39; — Vercel Deployment Protection Was the Culprit</title>
      <link>https://www.codeslog.com/en/posts/vercel-deployment-protection-zombie-task/</link>
      <pubDate>Fri, 24 Jul 2026 01:45:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/vercel-deployment-protection-zombie-task/</guid>
      <description>Right after launch, two audits sat stuck &amp;#39;scanning&amp;#39; for hours. Two fixes I was sure of missed, and only the third found the real culprit — Vercel Deployment Protection was blocking an internal call with a 401. A serverless queue debugging story.</description>
    </item>
  </channel>
</rss>
