mirror of
https://github.com/Lidarr/Lidarr.git
synced 2026-03-03 00:26:58 -05:00
Activity Queue does not load #4241
Labels
No labels
Area: API
Area: Database
Area: Db-migration
Area: Download Clients
Area: Extras
Area: Import Lists
Area: Indexer
Area: Metadata API
Area: Notifications
Area: Organizer
Area: Parser
Area: Scanning
Area: Tooling
Area: UI
Area: Unit Tests
Area: Update API
On Hold: MetadataAPI Blocking
Priority: High
Priority: Low
Priority: Medium
Status: Accepted
Status: Cannot Reproduce
Status: Confirmed
Status: Don't Merge
Status: Help Wanted
Status: In Progress
Status: Info Needed
Status: Investigating
Status: Logs Needed
Status: Maybe One Day
Status: Needs Triage
Status: On Hold
Status: Ready for Review
Status: Unlikely
Status: Waiting for OP
Status: Won't Fix
Type: Bug
Type: Documentation
Type: Duplicate
Type: Enhancement
Type: Enhancement
Type: External Bug
Type: Feature Request
Type: Regression
Type: Support
Type: Support.
conflict
conflict
no-conflict
not-pulled
radarr-pull
readarr-pull
sonarr upstream
sonarr-pull
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Lidarr-Lidarr#4241
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @hechz on GitHub (Jan 8, 2026).
Is there an existing issue for this?
Current Behavior
My activity queue shows 34 items next to the menu item. When I select the Activity Queue "Failed to load Queue" is displayed in the UI.
Expected Behavior
Queue should display active items
Steps To Reproduce
No response
Environment
What branch are you running?
Master
Trace Logs?
lidarr.trace.txt
Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.
trace- that are relevant and show this issue.@Ab30657 commented on GitHub (Jan 17, 2026):
Looking at the trace, multiple entries for artist "Fictional" seem to be present in your database. Knowingly or unknowingly for this case, this is a relevant future scenario where artists could have same name.
When trying to queue up, the entry for one of the release,
Some Great Contributionsfails due toReturnSingleArtistOrThrowwhich queries using thecleanNameof the artist, Fictional, throwing the exceptionThrowMoreThanOneMatchExceptionsince there are two entries.Recommendation
You can use the
disambiguationattribute available in musicbrainz to seperate the artists in a similar way you introduceddisambiguationattribute for albums on #490.The LOE could be higher than anticipated, will affect instances of names where disambiguation is necessary:
foreignArtistIdproperty suffixed).The search to Skyhook will remain unaffected because it uses the
foreignArtistIdproperty so will not create issue similar to #490.I will wait for the viewpoint of other folks regarding this for now.
There is already an disambiguation attribute on the Advanced settings of Media Management for Artists. The error is still because it looks for the clean name on the database. The Artist entity itself might require the disambiguation attribute like the Album entity in the db?
Temporary Fix
You might want to remove one of the artists folder for Fictional, and then your queue should be fine with the current queue having that only Fictional entry.