error-in-catalog-config are piling up in my Pipeline Template Catalogs

Last Reviewed:2025-10-06()
1 minute readKnowledge base

Issue

In my Pipeline Template Catalogs (PTC) section, I am seeing some entries with the name error-in-catalog-config1, error-in-catalog-config2, error-in-catalog-configN.

Environment

Explanation

Every entry with the name error-in-catalog-config$SOME_NUMBER corresponds to a real PTC that failed during the import process. Those entries appear either if you manually imported a PTC and failed, or if you already successfully imported a PTC and it failed because of its polling (configured in Check for template catalog updates every).

Resolution

First, check why your PTCs are failing during the import process. Once those import errors are fixed, there won’t be more error-in-catalog-config$SOME_NUMBER errors.

Then, you should manually remove all failed PTCs entries called error-in-catalog-config$SOME_NUMBER by clicking on each item in the Delete catalog dropdown option as shown in the following screenshot:

Tested product/plugin versions

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.