Stage Transform: Stage processing stopped early caused by: Error: preFetch check did not pass #637
Answered
by
FoxxMD
HappyLoLTroll
asked this question in
Q&A
|
Hi, LogConfig{
"cache": {
"valkey": "redis://valkey:6379"
},
"transformers": [
{
"type": "musicbrainz",
"name": "MyMB",
"data": {
"apis": [
{
"contact": "redacted"
}
],
"defaults": {
"releaseStatusPriority": ["pseudo-release", "official", "sensible", "native"],
"releaseAllowEmpty": true,
"forceSearch": true
}
}
}
],
"debugMode": false,
"disableWeb": false,
"sourceDefaults": {
"maxPollRetries": 2,
"maxRequestRetries": 2,
"retryMultiplier": 1.5
},
"clientDefaults": {
"maxRequestRetries": 2,
"retryMultiplier": 1.5
},
"sources": [
{
"type": "endpointlz",
"name": "LZ for Pano PC",
"id": "myLzPanoPC",
"enable": true,
"data": {
"token": "redacted"
}
},
{
"type": "endpointlz",
"name": "LZ for Mobile",
"id": "myLzMobile",
"enable": true,
"data": {
"token": "redacted"
}
},
{
"type": "endpointlz",
"name": "LZ for Pano Az",
"id": "myLz",
"enable": true,
"data": {
"token": "redacted"
}
}
],
"clients": [
{
"type": "listenbrainz",
"name": "Happy LZ Client",
"id": "brainzClient",
"enable": true,
"configureAs": "client",
"data": {
"token": "redacted",
"username": "redacted",
"url": "https://api.listenbrainz.org"
},
"options": {
"playTransform": {
"preCompare": [
{
"type": "musicbrainz",
"name": "MyMB"
}
]
}
}
},
{
"type": "lastfm",
"name": "Happy LFM Client",
"id": "myLastFmClient",
"enable": true,
"configureAs": "client",
"data": {
"apiKey": "redacted",
"secret": "redacted",
"redirectUri": "redacted"
},
"options": {
"playTransform": {
"preCompare": [
{
"type": "musicbrainz",
"name": "MyMB"
}
]
}
}
}]
}Am I missing something or there is a bug with this approach? I'm using Pano Scrobbler and have configured it to include only the primary artist, so that the MusicBrainz transform can add the remaining artists. The goal is to have LastFM scrobbles identical to those on Listenbrainz. Thanks |
Answered by
FoxxMD
Jul 14, 2026
Replies: 1 comment 3 replies
|
Thanks for the detailed logs! Can you try docker image and see if that resolves the error? |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Thanks for the reply and logs.
So the error was fixed because this is no longer showing up in the logs
The log line in your current logs