<?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[Support]]></title><description><![CDATA[A general support topic for all Inedo-related products and services including ProGet, BuildMaster, Otter, and more]]></description><link>https://forums.inedo.com/category/5</link><generator>RSS for Node</generator><lastBuildDate>Sun, 12 Jul 2026 20:46:47 GMT</lastBuildDate><atom:link href="https://forums.inedo.com/category/5.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 08 Jul 2026 07:01:33 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Maven snapshot metadata not generated for versions like TRK.0-SNAPSHOT]]></title><description><![CDATA[Hi @stevedennis,
Thank you very much for your answer. From what I've read elsewhere, that's exactly what I thought.
By the way, and besides that, ProGet is a really great tool. Good job !
Regards,
Olivier
]]></description><link>https://forums.inedo.com/topic/5793/maven-snapshot-metadata-not-generated-for-versions-like-trk-0-snapshot</link><guid isPermaLink="true">https://forums.inedo.com/topic/5793/maven-snapshot-metadata-not-generated-for-versions-like-trk-0-snapshot</guid><dc:creator><![CDATA[olivier.piron_7128]]></dc:creator><pubDate>Wed, 08 Jul 2026 07:01:33 GMT</pubDate></item><item><title><![CDATA[ProGet: Strategies for (more) flexible feed naming]]></title><description><![CDATA[Thanks for the tips. That Docker constraint is particularly good to know, I hadn't realized!
We do have a rather large amount of feeds to manage, including a (growing) set of feeds we use as local mirrors. I'll see if we can find an alternative solution that works for us...
]]></description><link>https://forums.inedo.com/topic/5792/proget-strategies-for-more-flexible-feed-naming</link><guid isPermaLink="true">https://forums.inedo.com/topic/5792/proget-strategies-for-more-flexible-feed-naming</guid><dc:creator><![CDATA[gbeckett]]></dc:creator><pubDate>Fri, 03 Jul 2026 12:58:07 GMT</pubDate></item><item><title><![CDATA[[ProGet] Feature Request: Expand which fields are settable when creating a Project using API&#x2F;PGUtil]]></title><link>https://forums.inedo.com/topic/5791/proget-feature-request-expand-which-fields-are-settable-when-creating-a-project-using-api-pgutil</link><guid isPermaLink="true">https://forums.inedo.com/topic/5791/proget-feature-request-expand-which-fields-are-settable-when-creating-a-project-using-api-pgutil</guid><pubDate>Fri, 03 Jul 2026 11:04:02 GMT</pubDate></item><item><title><![CDATA[[ProGet] Feature Request: Enable creating &#x27;Feed &amp; Project Groups&#x27; using API and&#x2F;or PGUtil]]></title><link>https://forums.inedo.com/topic/5790/proget-feature-request-enable-creating-feed-project-groups-using-api-and-or-pgutil</link><guid isPermaLink="true">https://forums.inedo.com/topic/5790/proget-feature-request-enable-creating-feed-project-groups-using-api-and-or-pgutil</guid><pubDate>Fri, 03 Jul 2026 10:16:58 GMT</pubDate></item><item><title><![CDATA[uploading debian package with plurl still required distrubtion]]></title><description><![CDATA[@manuel.riezebosch_8638 the purl argument was never actually read, so you could have really put anything in there :)
It was just one of those docs error; many other api endpoints will use a purl argument
And you're right... all the other package types have metadata inside the package, so that's what's read. Some require a file name, but Debian is an outlier in that it requires a distribution argument as well.
]]></description><link>https://forums.inedo.com/topic/5789/uploading-debian-package-with-plurl-still-required-distrubtion</link><guid isPermaLink="true">https://forums.inedo.com/topic/5789/uploading-debian-package-with-plurl-still-required-distrubtion</guid><dc:creator><![CDATA[dean-houston]]></dc:creator><pubDate>Tue, 30 Jun 2026 14:27:12 GMT</pubDate></item><item><title><![CDATA[Interacting with releases from otterscript, especially from within a scheduled job]]></title><description><![CDATA[Hi @stevedennis,
Can you provide more detail in your response?  You mention, for example, standard practices.  You don't however mention for what, what those are, or what features BuildMaster has to support them.  Maybe you mean in terms of doing things on a build bases.  If that is what you meant it might be helpful if you knew what I was doing which I unfortunately didn't provide in my original message.
The goal of my script is a clean up script for PRs since you guys do not have that feature built in. The purpose behind this is I want a PR to kick off a release/build to prove that it will actually build and set a marker on the PR to allow it to be merged.  Once the PR is merged those releases/builds are no longer useful.  Unfortunately, none of your retention rules take that in to consideration (part of why I asked in the previous message if you had any enhancements coming in the next major build that might be helpful for me). On your note about standard practices, I'm assuming this might be where it is targeted (the PR workflow).  One of our colleagues mentioned in another post trying things differently and even doing releaseless builds but they did support the idea of having some build verification on a PR before allowing it to be merged.  I'm not entirely sure, however, how a releaseless build might help.  I did think about it but my fear is making the UI more cumbersome in finding what you are looking for. What I mean by that is everything is listed together (although I haven't yet tried a mix of releases and releaseless builds but I will) so naturally the PRs would continue pushing the main release down.  Also if PR releases aren't being removed as soon as the PR is merged then the main release stays pushed down and there are more PRs to go through to find yours.
In my original message I left it a little more open to hopefully provide more flexibility in your response.  This time going to try a list of specific questions.

Do you have any upcoming features that might help with any of this?
The call to Releases_GetRelease requires a release id but fetching the releases just gives me release numbers. How do I bridge that gap?
What is the standard practices you referred to for the workflow?

I'm not sure I'll be able to before you respond but I do plan on investigating writing an extension for a different purpose anyways so I'll also look at one for this PR management too. In addition to the bullet points feel free to add anything you might find useful.
Thank you,
Brandon
]]></description><link>https://forums.inedo.com/topic/5788/interacting-with-releases-from-otterscript-especially-from-within-a-scheduled-job</link><guid isPermaLink="true">https://forums.inedo.com/topic/5788/interacting-with-releases-from-otterscript-especially-from-within-a-scheduled-job</guid><dc:creator><![CDATA[brandon_owensby_2976]]></dc:creator><pubDate>Mon, 29 Jun 2026 23:18:28 GMT</pubDate></item><item><title><![CDATA[npm package version falsely marked as vulnerable by ProGet]]></title><description><![CDATA[Hi Steve,
thanks for the explanation. I also think creating a PR for GHSA would be the best way to go. Since your company is incorporating GHSA into your product I think it's up to Inedo to improve GHSA by creating this PR, thus improving your product for you customers.
Thanks,
Andreas
]]></description><link>https://forums.inedo.com/topic/5787/npm-package-version-falsely-marked-as-vulnerable-by-proget</link><guid isPermaLink="true">https://forums.inedo.com/topic/5787/npm-package-version-falsely-marked-as-vulnerable-by-proget</guid><dc:creator><![CDATA[andreas.unverdorben_1551]]></dc:creator><pubDate>Mon, 29 Jun 2026 07:35:25 GMT</pubDate></item><item><title><![CDATA[Request to update PSCall documentation for getting data back from a ps1 asset]]></title><description><![CDATA[Glad I could help!
We'll get that documentation updated as well.
]]></description><link>https://forums.inedo.com/topic/5786/request-to-update-pscall-documentation-for-getting-data-back-from-a-ps1-asset</link><guid isPermaLink="true">https://forums.inedo.com/topic/5786/request-to-update-pscall-documentation-for-getting-data-back-from-a-ps1-asset</guid><dc:creator><![CDATA[gdivis]]></dc:creator><pubDate>Fri, 26 Jun 2026 23:03:39 GMT</pubDate></item><item><title><![CDATA[Install Issues - Docker Compose + Postgres]]></title><description><![CDATA[Hi @jeremy-oaks_9309 ,
Just wanted to respond to this real quick:

I have ~80k packages (~600GB) -- so we're opting for the stand-alone database for performance purposes

Based on this information we still recommend using the embedded database; it's almost always going to be more performant as well as simpler to maintain. 80k is not that many packages by any stretch.
While @pg_user_8607 is correct in that it's a bit easier to monitor database performance, investigate issues like bad queries, and do DBA maintenance tasks - that's all technically "our job". From a user perspective, the only required "database maintenance" should be backing up the files.
We certainly don't mind the help (and users like @pg_user_8607 have helped us out a lot!!), and it may be quicker if you "know what you're doing" to get to a root issue, since we're not all exactly experts at all these layers. But I just wanted to make sure you were aware of the pros-and-cons.
Thanks,
Steve
]]></description><link>https://forums.inedo.com/topic/5785/install-issues-docker-compose-postgres</link><guid isPermaLink="true">https://forums.inedo.com/topic/5785/install-issues-docker-compose-postgres</guid><dc:creator><![CDATA[stevedennis]]></dc:creator><pubDate>Fri, 26 Jun 2026 17:58:28 GMT</pubDate></item><item><title><![CDATA[Call to $CredentialProperty fails with &quot;not configured to allow access to encrypted values&quot; when it is]]></title><description><![CDATA[Hi @brandon_owensby_2976,
I wasn't able to reproduce this issue, but looking over the code, I can see a few scenarios in which "not configured to allow access to encrypted values" will trigger, even if that's not accurate. It's not trivial to rewrite that to provide a more accurate error message or credential resolution, so we'll add this to our BuildMAter 2027t roadmap and review it more closely then.
In the meantime, I would just use a variable and duplicate the information.
Thanks,
Steve
]]></description><link>https://forums.inedo.com/topic/5784/call-to-credentialproperty-fails-with-not-configured-to-allow-access-to-encrypted-values-when-it-is</link><guid isPermaLink="true">https://forums.inedo.com/topic/5784/call-to-credentialproperty-fails-with-not-configured-to-allow-access-to-encrypted-values-when-it-is</guid><dc:creator><![CDATA[stevedennis]]></dc:creator><pubDate>Thu, 25 Jun 2026 19:13:07 GMT</pubDate></item><item><title><![CDATA[Feature Request &#x2F; Discussion: Restricting Build Promotion to Forward-Only (Prevent Backward Promotion)]]></title><description><![CDATA[Hi @fabrice-mejean ,
Thanks so much for the detailed information and offer to connect further! Very interested in that and I will definitely take you up on that :)
Please give me a little time for that; I've got some travel coming up and then a bunch of other things... so I'd like to connect when I can really focus on some of these future things.
.
Cheers,
Alex
]]></description><link>https://forums.inedo.com/topic/5783/feature-request-discussion-restricting-build-promotion-to-forward-only-prevent-backward-promotion</link><guid isPermaLink="true">https://forums.inedo.com/topic/5783/feature-request-discussion-restricting-build-promotion-to-forward-only-prevent-backward-promotion</guid><dc:creator><![CDATA[apxltd]]></dc:creator><pubDate>Wed, 24 Jun 2026 10:25:08 GMT</pubDate></item><item><title><![CDATA[ProGet web requests stuck returning 500 &quot;Execution Timeout Expired&quot; while background tasks &amp; &#x2F;health stay healthy — requires restart]]></title><description><![CDATA[Hi @carl-westman_8110 ,
Thanks for sharing that. This isn't a symptom of "server overload" that we've seen before.
The error you shared is occurring on Feeds_GetFeeds, which is definitely not an intensive query, and I would not expect that to be timing out at all. It's just SELECT * FROM [Feeds].
However, that's a similar symptom to the "AzureSQL resource throttling" that we've seen on other users: another query is being throttled (for example, something that joins on [Feeds]), and that is causing a cascading impact on other queries.
We don't have enough information to say that's the case here. But, an easy way to test would be to up your DTUs substantially.
Otherwise, the next troubleshooting step is to try to identify the cause of the timeouts, which involves looking at HTTP Access logs and jobs occurring around the same time under Admin &gt; Scheduled Jobs.
Thanks,
Steve
]]></description><link>https://forums.inedo.com/topic/5782/proget-web-requests-stuck-returning-500-execution-timeout-expired-while-background-tasks-health-stay-healthy-requires-restart</link><guid isPermaLink="true">https://forums.inedo.com/topic/5782/proget-web-requests-stuck-returning-500-execution-timeout-expired-while-background-tasks-health-stay-healthy-requires-restart</guid><dc:creator><![CDATA[stevedennis]]></dc:creator><pubDate>Mon, 22 Jun 2026 11:42:01 GMT</pubDate></item><item><title><![CDATA[API request to get latest image or chart?]]></title><description><![CDATA[Hi @jeff-miles_5073 ,
You can get information about images and tags using the Docker API; we do not provide documentation on how to use that (see our caveat on Feed Endpoints). And unfortunately the Docker API is a bit awkward, but with enough ChatGPT you should be able to figure it out :)
You could also query the database directly, perhaps building some kind of data export tool so that you can sync it with your dashboard.
Hope that helps,
Alana
]]></description><link>https://forums.inedo.com/topic/5781/api-request-to-get-latest-image-or-chart</link><guid isPermaLink="true">https://forums.inedo.com/topic/5781/api-request-to-get-latest-image-or-chart</guid><dc:creator><![CDATA[atripp]]></dc:creator><pubDate>Fri, 19 Jun 2026 22:05:22 GMT</pubDate></item><item><title><![CDATA[ProGet pnpm audit reports no vulnerabilities]]></title><description><![CDATA[Hi @Ashley ,
Amazing, thanks for this investigation! This is very helpful.
You've also captured the exact issue we have with a lot of these APIs; no real specs (or worse... wrong specs), which involves a reverse engineering effort. This quote is wonderful:

In summary, due to the lack of an official JSON schema and potential changes between npm versions, it's crucial to treat the npm audit --json output structure as subject to change. Relying solely on the npm CLI source code for the most accurate and up-to-date information is recommended, along with implementing robust version checks and testing in your development processes.

Wouldn't it be nice if we could build our products like that! Anyway, I was curious and I asked internally, and the original engineer is almost certain that npmjs used to have the CVE number there, which we also used to emit until changing to PGVD number in ProGet 2023. But that is consistent with their position of "we don't do specs, just read the latest commit to figure it out.
But it doesn't really matter, that's what we have now...

To ensure consistency with the public npm registry, would it be possible to change ProGet to use a number for the id field on the audit response?

If you discovered this in ProGet 2025, we'd just change it in ProGet 2026 and not worry about it. But we need to be super-careful making API changes in a maintenance release. We can't quite get away with Microsoft/GitHub levels of quality :)
Seemingly harmless changes lead to broken builds, which are really painful to debug; for example, we recently added upload-time to PyPI API. That caused older versions of the pip client to break due to a bug in how they parsed dates.
There are probably too many client/versions to answer the question "what is this field even used for and what are the consequences of changing it?"
Perhaps an easier route is to just get pnmp to change to a string, like the rest of them? Or, just ignore it and "let it be"?
Over time, if you follow our recommend best practices, these audits will show fewer and fewer vulnerabilities. We plan to continuously refine the PVRS algorithm to better combat both "vulnslop" (i.e. AI-discovered and AI-generated vulnerabilities that cannot be exploited in any real-world scenario nor would cause any real-world harm if so) and misreporting.
Thanks,
Steve
]]></description><link>https://forums.inedo.com/topic/5780/proget-pnpm-audit-reports-no-vulnerabilities</link><guid isPermaLink="true">https://forums.inedo.com/topic/5780/proget-pnpm-audit-reports-no-vulnerabilities</guid><dc:creator><![CDATA[stevedennis]]></dc:creator><pubDate>Wed, 17 Jun 2026 10:38:18 GMT</pubDate></item><item><title><![CDATA[Cargo package metadata not parsing correctly causing builds to fail]]></title><description><![CDATA[Hi @joris-guex,
Thanks for sending an example over.  It looks like this is related to an issue in the libssh2-sys's manifest.  I have created a ticket, PG-3321, to handle these issues better.  We are expecting to have a fix out within the couple of maintenance releases of ProGet 2026.
Thanks,
Rich
]]></description><link>https://forums.inedo.com/topic/5779/cargo-package-metadata-not-parsing-correctly-causing-builds-to-fail</link><guid isPermaLink="true">https://forums.inedo.com/topic/5779/cargo-package-metadata-not-parsing-correctly-causing-builds-to-fail</guid><dc:creator><![CDATA[rhessinger]]></dc:creator><pubDate>Wed, 17 Jun 2026 06:28:25 GMT</pubDate></item><item><title><![CDATA[&quot;Invalid scheduled job type:&quot; (blank) in Update Checker Scheduled Job Dispatcher after 2025 → 2026 upgrade]]></title><description><![CDATA[Hi @svc-4x9p2a_6341 ,
This is known issue and will be addressed via PG-3309 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.
Thanks,
Steve
]]></description><link>https://forums.inedo.com/topic/5778/invalid-scheduled-job-type-blank-in-update-checker-scheduled-job-dispatcher-after-2025-2026-upgrade</link><guid isPermaLink="true">https://forums.inedo.com/topic/5778/invalid-scheduled-job-type-blank-in-update-checker-scheduled-job-dispatcher-after-2025-2026-upgrade</guid><dc:creator><![CDATA[stevedennis]]></dc:creator><pubDate>Tue, 16 Jun 2026 06:01:06 GMT</pubDate></item><item><title><![CDATA[User gets 500 error if you delete a logged in user]]></title><description><![CDATA[Hello,
Thanks for reporting this; this behavior is by design.
ProGet uses authentication tickets (i.e. encrypted cookies). If the username on a valid ticket cannot be located in the user directory, then a "user not found" error will occur, as it did here.
This errant behavior is generally desired for troubleshooting cases where users are intermittently not available from a user directory. Otherwise it's very difficult to troubleshoot, since it will just appear as a random log-out.
Thanks,
Steve
]]></description><link>https://forums.inedo.com/topic/5777/user-gets-500-error-if-you-delete-a-logged-in-user</link><guid isPermaLink="true">https://forums.inedo.com/topic/5777/user-gets-500-error-if-you-delete-a-logged-in-user</guid><dc:creator><![CDATA[stevedennis]]></dc:creator><pubDate>Fri, 12 Jun 2026 14:09:53 GMT</pubDate></item><item><title><![CDATA[ProGet 2026&#x2F;PostgreSQL (Embedded) Group Managed Service Account Support]]></title><description><![CDATA[Hi @mhelp_5176,
Connecting to the embedded database requires local access to the ProGet server. Once an attacker has that, then they already have full access to the database, as it's stored as files on disk... basically it's the equivalent of storing the safe key inside of the safe :)
As such. it doesn't make sense for us to add complexity to the product to support changing a password that's already secured.
Thanks,
Steve
]]></description><link>https://forums.inedo.com/topic/5776/proget-2026-postgresql-embedded-group-managed-service-account-support</link><guid isPermaLink="true">https://forums.inedo.com/topic/5776/proget-2026-postgresql-embedded-group-managed-service-account-support</guid><dc:creator><![CDATA[stevedennis]]></dc:creator><pubDate>Fri, 12 Jun 2026 03:09:10 GMT</pubDate></item><item><title><![CDATA[Support for Azure Key Vault references in Connector credentials]]></title><description><![CDATA[Hi @alkhleif_2585 ,
There isn't much demand for this kind of feature (I think we've only seen one or two requests for this over very many years) so it's not on our roadmap.
And it's unlikely we will add it to the roadmap considering that it would be quite costly to build, support, and maintain. Especially considering that we'd need to support all of the major "vaults" out there as well.
It doesn't seem to add much value to ProGet as these types of read-only credentials can be very long living (several years) without any security risk, and take just a few minutes to rotate when needed.
That being said, you could probably write a "sync script" pretty easily that continuously updates the connector credentials by connecting to the vault and then updating it via the API.
Cheers,
Steve
]]></description><link>https://forums.inedo.com/topic/5775/support-for-azure-key-vault-references-in-connector-credentials</link><guid isPermaLink="true">https://forums.inedo.com/topic/5775/support-for-azure-key-vault-references-in-connector-credentials</guid><dc:creator><![CDATA[stevedennis]]></dc:creator><pubDate>Wed, 10 Jun 2026 09:46:01 GMT</pubDate></item><item><title><![CDATA[Issue with Composer Connector: ProGet blocks non-standard version names from Packagist]]></title><description><![CDATA[Hi @vdubrovskyi_1854 ,
Without knowing which specific package you're referring to, it's hard to give a more specific example.
Historically, Packagist was effectively a database of "GitHub Repository pointers" and Composer was effectively just a wrapper around the Git client. They can both still operate in that mode, and needs to for older, non-standard packages. I suspect that's the type of package you're referring to here.
ProGet's Composer feeds work with "packages" (i.e. not the GitHub pointers), which account for nearly all of the modern packages on Packagist.org. For the small number of packages that don't follow the standard (mostly older, legacy packages), you'll need to download them, properly package them, and then upload them to follow the standard.
Unfortunately there's no technically feasible/sensible way to solve this problem - since it would require ProGet to serve as a GitHub pointer database, which just doesn't make sense.
Cheers,
Steve
]]></description><link>https://forums.inedo.com/topic/5774/issue-with-composer-connector-proget-blocks-non-standard-version-names-from-packagist</link><guid isPermaLink="true">https://forums.inedo.com/topic/5774/issue-with-composer-connector-proget-blocks-non-standard-version-names-from-packagist</guid><dc:creator><![CDATA[stevedennis]]></dc:creator><pubDate>Tue, 09 Jun 2026 15:04:15 GMT</pubDate></item><item><title><![CDATA[Block recently published - Metadata filter ?]]></title><description><![CDATA[@jens-viebig_4541 ooh good catch!
That guidance is outdated as of ProGet 2026, where we no longer recommend/default to blocking Noncompliant packages.
We should rewrite/republish the article to be more focused on guidance, update the screenshots, etc. I'll add that to the list.
]]></description><link>https://forums.inedo.com/topic/5773/block-recently-published-metadata-filter</link><guid isPermaLink="true">https://forums.inedo.com/topic/5773/block-recently-published-metadata-filter</guid><dc:creator><![CDATA[apxltd]]></dc:creator><pubDate>Tue, 09 Jun 2026 09:44:30 GMT</pubDate></item><item><title><![CDATA[[feature] ProGet: Send test notifications from &#x27;Notifiers &amp; Webhooks&#x27;]]></title><description><![CDATA[@sigurd-hansen_7559 wow very cool! We didn't anticipate anyone would customize these templates beyond adding a variable or two, so it it didn't seem to make a lot of sense to invest in a proper editor (like we have in the other products)
Anyway, it'd be interesting to see what kind of templates you develop.
]]></description><link>https://forums.inedo.com/topic/5772/feature-proget-send-test-notifications-from-notifiers-webhooks</link><guid isPermaLink="true">https://forums.inedo.com/topic/5772/feature-proget-send-test-notifications-from-notifiers-webhooks</guid><dc:creator><![CDATA[stevedennis]]></dc:creator><pubDate>Mon, 08 Jun 2026 09:54:20 GMT</pubDate></item><item><title><![CDATA[Cargo feed returning 500 Internal Server Error]]></title><description><![CDATA[Hi @atripp,
We have now updated to ProGet 2026.3 and can confirm this is now working as expected. Thank you for your prompt help.
]]></description><link>https://forums.inedo.com/topic/5771/cargo-feed-returning-500-internal-server-error</link><guid isPermaLink="true">https://forums.inedo.com/topic/5771/cargo-feed-returning-500-internal-server-error</guid><dc:creator><![CDATA[joris.guex]]></dc:creator><pubDate>Fri, 05 Jun 2026 00:48:48 GMT</pubDate></item><item><title><![CDATA[Container image size calculation does not always work]]></title><description><![CDATA[Thank you very much for the detailed answer!
]]></description><link>https://forums.inedo.com/topic/5770/container-image-size-calculation-does-not-always-work</link><guid isPermaLink="true">https://forums.inedo.com/topic/5770/container-image-size-calculation-does-not-always-work</guid><dc:creator><![CDATA[pg_user_8607]]></dc:creator><pubDate>Tue, 02 Jun 2026 07:17:14 GMT</pubDate></item><item><title><![CDATA[Scheduled Task is failing due to invalid script identifier]]></title><description><![CDATA[Hi Alana,
Just wanted to let you know that restarting the service did fix the issue.  Thank you for the suggestion.
Brandon
]]></description><link>https://forums.inedo.com/topic/5769/scheduled-task-is-failing-due-to-invalid-script-identifier</link><guid isPermaLink="true">https://forums.inedo.com/topic/5769/scheduled-task-is-failing-due-to-invalid-script-identifier</guid><dc:creator><![CDATA[brandon_owensby_2976]]></dc:creator><pubDate>Tue, 02 Jun 2026 04:19:29 GMT</pubDate></item></channel></rss>