Sync State
Summary
The sync state in Recyclarr allows it to more accurately detect changes to custom formats in the TRaSH guides. This mainly helps cover changes done on the *arr side, like renames.
Once Recyclarr creates or updates a custom format in *arr, it records information about it in a
state file located in the state subdirectory under the main app data location. The location
varies depending on platform.
The state files are not meant to be edited by users. In general I recommend leaving them alone. Recyclarr will manage it for you.
Relocating Server Instances
Sometimes users relocate an instance of Radarr or Sonarr. They then update the base_url
configuration property to have Recyclarr communicate with that service at its new location.
Recyclarr uniquely identifies an instance by its base_url value. If the hostname, port, path,
scheme, or any other part of the URL changes (including adding or removing a trailing slash!),
Recyclarr will no longer use the previous state data and instead will create a new one.
Recyclarr handles this automatically. On the next sync, it detects that configured resources already exist in the service by name and adopts them, emitting a warning for each one:
CF 'CRiT' already existed in the service and was replaced by Recyclarr
No manual intervention is required. Recyclarr resumes managing the resources it previously created.
Ambiguous Matches
If the service contains multiple resources with the same name (differing only in case, such as "HULU" and "hulu"), Recyclarr cannot determine which one to adopt. The sync error instructs you to delete or rename the duplicates in Sonarr/Radarr so each name is unique.