Manual Imports do not trigger 'On Release Import' notification event #2900

New issue

Open

opened 2026-02-20 02:12:55 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-20 02:12:55 -05:00

Owner

Originally created by @CPU-Blanc on GitHub (May 9, 2023).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

Manually importing a track/album does not trigger the "On Release Import" event in Connections to fire. It appears to only trigger the retagged event.

Expected Behavior

Manual Imports to trigger the "On Release Import" event, much like it does with Sonarr.

Steps To Reproduce

Add an album to the Lidarr database (Library > Add New)
Import the tracks manually via Wanted > Manual Import
Observe no "On Release Import" event being sent in Connecitons

Environment

- OS: Windows Server 2016
- Lidarr: 1.2.0.3168
- Docker Install: No
- Using Reverse Proxy: Yes
- Browser: Google Chrome
- Database: Sqlite 3.36.0

What branch are you running?

Nightly

Trace Logs?

trace.txt

Specifically:

2023-05-07 18:38:05.8|Trace|EventAggregator|Publishing TrackFileRetaggedEvent
2023-05-07 18:38:05.8|Trace|EventAggregator|TrackFileRetaggedEvent -> NotificationService
2023-05-07 18:38:05.8|Trace|EventAggregator|TrackFileRetaggedEvent <- NotificationService
2023-05-07 18:38:05.8|Trace|EventAggregator|TrackFileRetaggedEvent -> EntityHistoryService
2023-05-07 18:38:05.8|Trace|EventAggregator|TrackFileRetaggedEvent <- EntityHistoryService
2023-05-07 18:38:05.8|Trace|ConfigService|Using default config value for 'importextrafiles' defaultValue:'False'
2023-05-07 18:38:05.9|Trace|EventAggregator|Publishing TrackFileAddedEvent
2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent -> TrackFileController
2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent <- TrackFileController
2023-05-07 18:38:05.9|Trace|EventAggregator|Publishing TrackFileAddedEvent
2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent -> TrackFileController
2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent <- TrackFileController
2023-05-07 18:38:05.9|Trace|EventAggregator|Publishing TrackFileAddedEvent
2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent -> TrackFileController
2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent <- TrackFileController
2023-05-07 18:38:05.9|Trace|EventAggregator|Publishing TrackFileAddedEvent
2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent -> TrackFileController
2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent <- TrackFileController
2023-05-07 18:38:05.9|Trace|EventAggregator|Publishing TrackFileAddedEvent
2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent -> TrackFileController
2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent <- TrackFileController
2023-05-07 18:38:05.9|Debug|ImportApprovedTracks|Inserted new trackfiles in 43ms

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

I have followed the steps in the wiki link above and provided the required trace logs that are relevant and show this issue.

Originally created by @CPU-Blanc on GitHub (May 9, 2023). ### Is there an existing issue for this? - [X] I have searched the existing open and closed issues ### Current Behavior Manually importing a track/album does not trigger the "On Release Import" event in Connections to fire. It appears to only trigger the retagged event. ### Expected Behavior Manual Imports to trigger the "On Release Import" event, much like it does with Sonarr. ### Steps To Reproduce 1. Add an album to the Lidarr database (Library > Add New) 2. Import the tracks manually via Wanted > Manual Import 3. Observe no "On Release Import" event being sent in Connecitons ### Environment ```markdown - OS: Windows Server 2016 - Lidarr: 1.2.0.3168 - Docker Install: No - Using Reverse Proxy: Yes - Browser: Google Chrome - Database: Sqlite 3.36.0 ``` ### What branch are you running? Nightly ### Trace Logs? [trace.txt](https://github.com/Lidarr/Lidarr/files/11435521/trace.txt) Specifically: ``` 2023-05-07 18:38:05.8|Trace|EventAggregator|Publishing TrackFileRetaggedEvent 2023-05-07 18:38:05.8|Trace|EventAggregator|TrackFileRetaggedEvent -> NotificationService 2023-05-07 18:38:05.8|Trace|EventAggregator|TrackFileRetaggedEvent <- NotificationService 2023-05-07 18:38:05.8|Trace|EventAggregator|TrackFileRetaggedEvent -> EntityHistoryService 2023-05-07 18:38:05.8|Trace|EventAggregator|TrackFileRetaggedEvent <- EntityHistoryService 2023-05-07 18:38:05.8|Trace|ConfigService|Using default config value for 'importextrafiles' defaultValue:'False' 2023-05-07 18:38:05.9|Trace|EventAggregator|Publishing TrackFileAddedEvent 2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent -> TrackFileController 2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent <- TrackFileController 2023-05-07 18:38:05.9|Trace|EventAggregator|Publishing TrackFileAddedEvent 2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent -> TrackFileController 2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent <- TrackFileController 2023-05-07 18:38:05.9|Trace|EventAggregator|Publishing TrackFileAddedEvent 2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent -> TrackFileController 2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent <- TrackFileController 2023-05-07 18:38:05.9|Trace|EventAggregator|Publishing TrackFileAddedEvent 2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent -> TrackFileController 2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent <- TrackFileController 2023-05-07 18:38:05.9|Trace|EventAggregator|Publishing TrackFileAddedEvent 2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent -> TrackFileController 2023-05-07 18:38:05.9|Trace|EventAggregator|TrackFileAddedEvent <- TrackFileController 2023-05-07 18:38:05.9|Debug|ImportApprovedTracks|Inserted new trackfiles in 43ms ``` ### Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided. - [X] I have followed the steps in the wiki link above and provided the required trace logs that are relevant and show this issue.