Hi all,
I’ve run into a problem when Mylar sends search queries to Prowlarr. For example, if I search for "Judge Dredd The Complete Case Files #45" Mylar sends the query to Prowlarr as: judge dredd complete case files 045
The issue is that the leading zero (045) causes Prowlarr not to return any results. However, if I manually search in Prowlarr for "judge dredd complete case files 45" it works correctly and returns results.
in prowlarr log when mylar sends a requset:
2025-04-12 13:12:17.3|Info|ReleaseSearchService|Searching indexer(s): [MyAnonamouse] for Term: [judge dredd complete case files 040], Offset: 0, Limit: 0, Categories: [7030]
also search for alternative name:
2025-04-12 13:12:17.5|Info|ReleaseSearchService|Searching indexer(s): [MyAnonamouse] for Term: [complete case files 040], Offset: 0, Limit: 0, Categories: [7030]
Is there a way to configure Mylar to strip or avoid sending leading zeros in issue numbers when querying?
I’m using the Version: v0.8.2 (master)
Thanks!
Prevent sending leading zeros in issue numbers
-
- Posts: 1
- Joined: Sat Apr 12, 2025 11:23 am
- evilhero
- Site Admin
- Posts: 2904
- Joined: Sat Apr 20, 2013 3:43 pm
- Contact:
Re: Prevent sending leading zeros in issue numbers
No there isn't a way. If you hadn't noticed after posting this, or maybe missed it, mylar will iterate over the various issue number padding (040, 40) against the main series naming, as well as doing the same with any and all alternate naming that may exist.
This is because it has to do text based queries, which you've found out is a limitation when it comes to querying things (40 getting a hit, 040 not). It will eventually cycle thru and get to the other issue number without padding, but usually with a delay of anywhere from 30s to 1min between searches (and yes this delay is intentional).
If it's not getting results after the iterations, than odds are it's either due to your prowlarr mapping the incorrect category on myanon to 7030, or possibly a naming exception that's being triggered to make it reject it (there's a section in the configuration that allows to you to define search term exclusions).
This is because it has to do text based queries, which you've found out is a limitation when it comes to querying things (40 getting a hit, 040 not). It will eventually cycle thru and get to the other issue number without padding, but usually with a delay of anywhere from 30s to 1min between searches (and yes this delay is intentional).
If it's not getting results after the iterations, than odds are it's either due to your prowlarr mapping the incorrect category on myanon to 7030, or possibly a naming exception that's being triggered to make it reject it (there's a section in the configuration that allows to you to define search term exclusions).