<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[&quot;Invalid scheduled job type:&quot; (blank) in Update Checker Scheduled Job Dispatcher after 2025 → 2026 upgrade]]></title><description><![CDATA[<p dir="auto">Hi all,</p>
<p dir="auto">Since upgrading from ProGet 2025 to 2026 on June 1, the Scheduled Job Dispatcher logs this once per run:</p>
<p dir="auto"><strong>ERROR: 2026-06-16 05:28:05Z - Invalid scheduled job type:</strong></p>
<p dir="auto">The job type after the colon is empty. Package restore/publish works normally for all clients, so there's no feed-serving impact — it looks like an orphaned or null-typed scheduled-task row left over from the upgrade/migration.</p>
<p dir="auto">Environment</p>
<ul>
<li>ProGet 2026.4 (Build 10), DB schema 26.0.4.10</li>
<li>PostgreSQL 17.10 (integrated), Ubuntu 24.04, collation C (UTF8)</li>
</ul>
<p dir="auto">Questions</p>
<ul>
<li>Is this a known issue/regression after the 2025 → 2026 upgrade (is there a tracked PG-####)?</li>
<li>What's the supported way to identify and fix the offending scheduled-task row? I'd prefer not to edit the database directly on a production instance.</li>
</ul>
<p dir="auto">Thanks!</p>
]]></description><link>https://forums.inedo.com/topic/5778/invalid-scheduled-job-type-blank-in-update-checker-scheduled-job-dispatcher-after-2025-2026-upgrade</link><generator>RSS for Node</generator><lastBuildDate>Wed, 17 Jun 2026 03:20:55 GMT</lastBuildDate><atom:link href="https://forums.inedo.com/topic/5778.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 16 Jun 2026 06:01:06 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to &quot;Invalid scheduled job type:&quot; (blank) in Update Checker Scheduled Job Dispatcher after 2025 → 2026 upgrade on Tue, 16 Jun 2026 06:01:06 GMT]]></title><description><![CDATA[<p dir="auto">Hi all,</p>
<p dir="auto">Since upgrading from ProGet 2025 to 2026 on June 1, the Scheduled Job Dispatcher logs this once per run:</p>
<p dir="auto"><strong>ERROR: 2026-06-16 05:28:05Z - Invalid scheduled job type:</strong></p>
<p dir="auto">The job type after the colon is empty. Package restore/publish works normally for all clients, so there's no feed-serving impact — it looks like an orphaned or null-typed scheduled-task row left over from the upgrade/migration.</p>
<p dir="auto">Environment</p>
<ul>
<li>ProGet 2026.4 (Build 10), DB schema 26.0.4.10</li>
<li>PostgreSQL 17.10 (integrated), Ubuntu 24.04, collation C (UTF8)</li>
</ul>
<p dir="auto">Questions</p>
<ul>
<li>Is this a known issue/regression after the 2025 → 2026 upgrade (is there a tracked PG-####)?</li>
<li>What's the supported way to identify and fix the offending scheduled-task row? I'd prefer not to edit the database directly on a production instance.</li>
</ul>
<p dir="auto">Thanks!</p>
]]></description><link>https://forums.inedo.com/post/19792</link><guid isPermaLink="true">https://forums.inedo.com/post/19792</guid><dc:creator><![CDATA[svc-4x9p2a_6341]]></dc:creator><pubDate>Tue, 16 Jun 2026 06:01:06 GMT</pubDate></item><item><title><![CDATA[Reply to &quot;Invalid scheduled job type:&quot; (blank) in Update Checker Scheduled Job Dispatcher after 2025 → 2026 upgrade on Tue, 16 Jun 2026 15:01:05 GMT]]></title><description><![CDATA[<p dir="auto">Hi <a class="plugin-mentions-user plugin-mentions-a" href="https://forums.inedo.com/uid/3862">@svc-4x9p2a_6341</a> ,</p>
<p dir="auto">This is known issue and will be addressed via <a href="https://issues.inedo.com/issue/PG-3309" class="inedo-link inedo-link-pg" rel="nofollow">PG-3309</a> in the next maintenance release. You can just ignore the messages for the time being, it only happens like once a week or so.... I wouldn't modify the database either.</p>
<p dir="auto">Thanks,<br />
Steve</p>
]]></description><link>https://forums.inedo.com/post/19795</link><guid isPermaLink="true">https://forums.inedo.com/post/19795</guid><dc:creator><![CDATA[stevedennis]]></dc:creator><pubDate>Tue, 16 Jun 2026 15:01:05 GMT</pubDate></item></channel></rss>