A “custom format not found” or “TRaSH ID not found” message usually means Recyclarr cannot locate the custom format, quality profile, or other TRaSH Guides resource referenced by your configuration. The problem is often caused by an incorrect ID, outdated configuration, a typo in the resource name, or a mismatch between the resource you are trying to synchronize and the Sonarr or Radarr instance being targeted.
TRaSH IDs are commonly used in Recyclarr configurations because they provide a stable way to identify custom formats and other resources from the TRaSH Guides ecosystem. Recyclarr uses those identifiers to determine which definitions should be synchronized. If an ID does not exist in the available data, has been entered incorrectly, belongs to a different resource, or is no longer available, Recyclarr cannot resolve it and the synchronization process may stop or skip that item.
What Does “Custom Format Not Found” Mean in Recyclarr?
A custom format is a Sonarr or Radarr rule that can assign scores or match specific media characteristics. Recyclarr can synchronize predefined custom formats based on definitions from TRaSH Guides.
A typical configuration may reference a custom format using a TRaSH ID:
custom_formats:
- trash_ids:
- abcdef1234567890abcdef1234567890
The trash_ids value tells Recyclarr which custom format definition to use.
If Recyclarr reports that the custom format or TRaSH ID was not found, it means the identifier could not be resolved against the resource definitions available to Recyclarr.
The error does not necessarily mean that Sonarr or Radarr itself is broken. In many cases, the issue exists entirely within the Recyclarr configuration or the referenced TRaSH resource.
Why Does Recyclarr Say a TRaSH ID Was Not Found?
Several configuration problems can produce this message. The most common causes are an incorrect ID, a typo, an outdated configuration, or using an identifier that belongs to a different resource.
The TRaSH ID Is Incorrect
TRaSH IDs are long identifiers, so a single missing or changed character can prevent Recyclarr from finding the resource.
For example:
trash_ids:
- abcdef1234567890abcdef1234567890
If the actual identifier is different, Recyclarr cannot match it to a known custom format.
Check the ID carefully rather than manually typing it whenever possible.
The ID Contains a Typo
YAML indentation errors are common, but the identifier itself can also contain a typo.
For example:
trash_ids:
- 1234567890abcdef1234567890abcde
Even if the surrounding configuration is valid YAML, an incorrect TRaSH ID will still fail during resource lookup.
Copy the identifier directly from the relevant TRaSH Guides resource or from a current Recyclarr configuration reference.
The Configuration Is Outdated
TRaSH Guides configurations can change over time. Custom formats may be updated, renamed, replaced, reorganized, or removed.
A configuration copied from an older guide or tutorial can therefore contain references that are no longer valid.
This is especially relevant if the configuration was created months or years ago and has not been reviewed since.
Instead of assuming that every old ID remains valid indefinitely, compare your configuration with the current resource definition.
Is the Custom Format Name the Same as the TRaSH ID?
No. A custom format has a human-readable name and an identifier.
For example, a configuration may use:
trash_ids:
- 1234567890abcdef1234567890abcdef
while the corresponding custom format has a readable name in Sonarr or Radarr.
The name is useful for identifying the rule, but Recyclarr’s trash_ids reference is an identifier.
Changing the displayed name in Sonarr or Radarr does not mean you should replace the TRaSH ID with that name.
A common mistake is to write:
trash_ids:
- My Custom Format
when the configuration expects a valid TRaSH ID.
Use the appropriate identifier instead.
Check Whether You Are Using the Correct Resource Type
Not every TRaSH ID represents the same kind of resource.
Recyclarr configurations can contain different types of resources, including custom formats and quality-related definitions. An identifier intended for one resource should not automatically be placed in another configuration section.
For example, a custom format ID belongs under the custom format configuration rather than being treated as a quality profile ID.
Incorrect:
quality_profiles:
- trash_ids:
- <custom-format-id>
The exact structure depends on the Recyclarr configuration schema and the resource being referenced.
When an ID is reported as missing, first confirm what type of TRaSH resource that ID represents.
Check the Recyclarr Configuration Structure
A valid TRaSH ID can still cause problems if it is placed in the wrong section.
For example:
custom_formats:
- trash_ids:
- <valid-custom-format-id>
The YAML structure must match the Recyclarr configuration schema.
Check:
- indentation
- section names
- list formatting
trash_idsplacement- instance configuration
- profile configuration
- quotation marks where required
YAML is sensitive to indentation, so moving a value by one level can change how Recyclarr interprets the configuration.
Verify the TRaSH ID From the Current Source
One of the most reliable ways to troubleshoot a missing ID is to verify it against the current TRaSH Guides definition.
Do not rely solely on an old blog post, YouTube tutorial, GitHub snippet, or copied configuration.
Compare the following:
Your configuration
↓
TRaSH ID
↓
Current resource definition
↓
Custom format/resource name
If the ID in your YAML does not match the current definition, replace it with the correct identifier.
This is particularly important when maintaining a configuration that was originally copied from another user’s setup.
What If the Custom Format Exists in Sonarr or Radarr?
A custom format can exist inside Sonarr or Radarr while Recyclarr still reports that its TRaSH ID was not found.
These are separate things.
Sonarr or Radarr stores the custom format on your media server. Recyclarr uses its own configuration and resource definitions to determine what it should synchronize.
For example, you may already have a custom format called:
Preferred Audio
inside Radarr.
That does not automatically mean Recyclarr can identify it through an arbitrary TRaSH ID.
If the configuration references a TRaSH ID that Recyclarr cannot resolve, the existing custom format inside Radarr does not fix the lookup error.
Check Whether the Resource Was Removed or Replaced
TRaSH Guides resources can evolve. A custom format that existed in an older configuration may later be replaced or removed.
If your configuration references an old ID, Recyclarr may no longer be able to resolve it.
In that situation, searching for the exact old ID may not be enough. Check the current TRaSH Guides configuration and determine whether:
- The same custom format still exists.
- The custom format has a new identifier.
- The rule has been renamed.
- The rule has been replaced by another format.
- The old resource is no longer supported.
Updating the configuration to the current resource is usually preferable to continuing to use an obsolete identifier.
Check Your Recyclarr Version
An older Recyclarr release can also complicate troubleshooting.
If your configuration follows current documentation but your installed Recyclarr version is significantly older, the configuration syntax or supported resources may differ.
Check the installed version:
recyclarr --version
If you are running Recyclarr through Docker, check the image/version you are actually using rather than assuming that your local configuration determines the application version.
For example:
docker compose run --rm recyclarr --version
The exact command can vary depending on your Docker setup.
Keeping Recyclarr reasonably current can reduce compatibility problems when working with current configuration formats.
Check the Configuration File You Are Actually Using
A surprisingly common problem is editing one YAML file while Recyclarr is reading another.
For example, you might modify:
./recyclarr.yml
but your command may be using a different configuration location.
When troubleshooting, confirm:
- the file path
- the active configuration
- the Docker volume mapping
- the working directory
- the selected instance
- any command-line configuration options
If the error continues after you correct an ID, verify that the corrected file is the one Recyclarr is loading.
Multiple Sonarr or Radarr Instances Can Cause Confusion
Multiple instances make configuration errors harder to identify.
A setup might contain separate instances for:
Sonarr Movies
Sonarr TV
Radarr 4K
Radarr HD
A custom format can be valid for one synchronization target while the configuration or profile setup for another target is different.
If you use multiple instances, isolate the failing synchronization where possible.
For example:
recyclarr sync sonarr
or use the relevant instance-selection options supported by your configuration.
This helps determine whether the problem affects the resource itself or only one configuration.
Use Debug Logging to Find the Exact Resource
Normal output may tell you that a TRaSH ID was not found, but debug logging can provide more context.
For example:
recyclarr sync --log debug
Or use the appropriate command structure for the instance you are troubleshooting.
Look for information showing:
- the configuration file being loaded
- the selected instance
- the resource being processed
- the TRaSH ID being resolved
- the custom format associated with the ID
- the point where lookup fails
The goal is to identify the exact identifier that Recyclarr cannot resolve instead of changing multiple configuration sections at once.
Common YAML Mistakes With Custom Formats
Several YAML mistakes repeatedly appear in Recyclarr configurations.
Incorrect list formatting
Correct list structure generally looks like:
trash_ids:
- id-one
- id-two
- id-three
Do not accidentally turn multiple IDs into one malformed value.
Incorrect indentation
For example:
custom_formats:
- trash_ids:
- id-one
and:
custom_formats:
- trash_ids:
- id-one
may not be equivalent in every surrounding configuration structure. Follow the schema expected by your Recyclarr version and configuration type rather than relying on formatting from an unrelated example.
Accidental characters
Watch for:
spaces
commas
quotes
extra characters
copied punctuation
inside the ID.
A TRaSH ID should be copied exactly.
Do Not Replace TRaSH IDs With Random Custom Format IDs
Sonarr and Radarr have their own internal identifiers for objects stored in the application.
Those IDs should not automatically be substituted for TRaSH IDs in a Recyclarr configuration.
Recyclarr’s trash_ids references are intended to identify TRaSH resources. An internal Sonarr or Radarr identifier is a different concept.
If you manually replace a TRaSH ID with an application-generated ID, the configuration can become invalid even though the custom format exists in the application.
What If You Created the Custom Format Yourself?
If you created a custom format manually in Sonarr or Radarr, it may not have a corresponding TRaSH ID.
In that case, you generally should not invent a trash_ids value for it.
A manually created custom format and a TRaSH Guides custom format are different configuration paths. If you want Recyclarr to manage your own custom format, use the configuration mechanism appropriate for custom definitions rather than pretending the format has a TRaSH identifier.
This distinction is important when combining community configurations with custom rules.
A Practical Troubleshooting Process
The fastest approach is to troubleshoot the lookup rather than rebuilding the entire configuration.
Start with the exact error message and identify the missing identifier.
Then check the ID:
1. Copy the reported TRaSH ID.
2. Compare it with the current resource.
3. Confirm that it belongs to a custom format.
4. Check whether the resource still exists.
5. Verify the YAML section.
6. Confirm the configuration file being loaded.
7. Run Recyclarr again.
If the ID is obsolete, update the configuration using the current resource definition.
If the ID is correct, investigate the Recyclarr version and configuration structure.
If only one instance fails, inspect that instance’s configuration rather than changing every Sonarr or Radarr definition.
Should You Delete the Custom Format From Sonarr or Radarr?
Not necessarily.
A “TRaSH ID not found” message is primarily a resource-resolution problem. Deleting custom formats from Sonarr or Radarr without understanding the cause can create additional configuration work.
First determine why Recyclarr cannot resolve the referenced resource.
If the custom format was previously created by Recyclarr and you are trying to replace an outdated definition, follow the appropriate migration or synchronization process rather than deleting objects blindly.
How to Prevent TRaSH ID Errors
Keeping your configuration organized makes these problems easier to avoid.
Use current documentation when adding new resources, copy identifiers carefully, and avoid maintaining large blocks of IDs from old tutorials without reviewing them.
It also helps to keep comments near groups of custom formats:
custom_formats:
# Audio preferences
- trash_ids:
- <audio-format-id>
# HDR preferences
- trash_ids:
- <hdr-format-id>
Comments do not affect the identifier, but they make future maintenance easier.
You should also review configurations after major changes to your Recyclarr setup, Sonarr/Radarr configuration, or the underlying TRaSH Guides definitions.
Frequently Asked Questions
Why does Recyclarr say my custom format was not found?
Usually because the referenced TRaSH ID cannot be resolved. Check for a typo, outdated ID, incorrect resource type, or an invalid configuration structure.
Can I use the custom format name instead of a TRaSH ID?
Not when the configuration field specifically expects a trash_ids value. Use the identifier required by the relevant Recyclarr configuration.
Why does the custom format exist in Radarr but Recyclarr cannot find it?
The custom format stored in Radarr and the TRaSH resource referenced by Recyclarr are not the same lookup mechanism. Recyclarr must be able to resolve the configured TRaSH ID independently.
Can an old TRaSH ID stop working?
Yes. If a resource has been removed, replaced, or reorganized, an older configuration may contain an identifier that is no longer available.
Should I create a new TRaSH ID for my custom format?
No. TRaSH IDs identify existing TRaSH resources. A custom format you create yourself should be configured through the appropriate custom-format configuration rather than using a fabricated identifier.
How can I identify which TRaSH ID is causing the error?
Read the exact error output and use debug logging if necessary. Then compare the reported identifier against the current resource definitions and your YAML configuration.
Conclusion
A missing custom format or TRaSH ID error usually comes down to resource identification rather than a problem with Sonarr or Radarr. The first things to check are the exact ID, its spelling, whether the resource still exists, and whether it belongs in the configuration section where you placed it. Outdated configurations are another common source of failures, particularly when IDs were copied from older guides or examples.
Work through the error one identifier at a time, verify the current resource, confirm that Recyclarr is loading the configuration you edited, and use debug logging when the normal output does not provide enough detail. This approach avoids unnecessary changes and makes it easier to keep your Recyclarr configuration synchronized with current TRaSH resources.