Mod Organizer 2 - "Check for updates" multiple errors returned but some updates downloaded anyway

[Octopodulus]

EDIT: For those who get the same errors and find this post, you can find others reporting this error here:

Go to the MO2 Discord, via their site: https://www.modorganizer.org/

Search this channel: #issue-reports

For this text: You have mods that haven't been checked within the last month using the new API

END EDIT.

I have noticed an error popping up at the bottom of MO2 each time I use the Check for updates feature.

I've renewed by API key and tried again, but it has made no difference.

When I changed logging to "debug" in MO2, I get the following output in the log each time I click on the "Check for udpates" option:

Quote

 

[2024-04-22 01:07:28.326 I] You have mods that haven't been checked within the last month using the new API. These mods must be checked before we can use the bulk update API. This will consume significantly more API requests than usual. You will need to rerun the update check once complete in order to parse the remaining mods.

[2024-04-22 01:07:28.369 E] request (https://api.nexusmods.com/v1/games/cyberpunk2077/mods/550/files) error: Error transferring https://api.nexusmods.com/v1/games/cyberpunk2077/mods/550/files - server replied:  (201)

[2024-04-22 01:07:28.369 D] Error 403: Request to Nexus failed: Error transferring https://api.nexusmods.com/v1/games/cyberpunk2077/mods/550/files - server replied:

 

Is there actually a problem here, or is this just an erroneous message that can be ignored?

 

[Pickysaurus]

I'm afraid we can't provide support with Mod Organizer 2. You can ask the developers of that mod manager. 

[Octopodulus]

Thanks for your reponse. I've updated my post with useful info for others.

[Octopodulus]

ok - so for me it was this error that was more useful to resolve:

Quote

[2024-04-22 14:48:24.929 D] Error 403: Request to Nexus failed: Error transferring https://api.nexusmods.com/v1/games/skyrimspecialedition/mods/502/files - server replied:

Because this one actually tells you the mod number it's looking for. In this case "502".

If it can't link to mod number 502 for SkyrimSE on Nexus Mods website (you can test this by editing the number at the end of another modpage's URL), you might get the above error.

You can change the mod number manually in the mod's information in MO2 to -1 and it will be ignored in future updates, hence resolving the error. Make a note that this is a mod you will have to periodically check manually for any updates.

In my case it's because the mod that's returninng the error in MO2 is not found under "SkyrimSE" on Nexus, it's a site modding tool instead: https://www.nexusmods.com/site/mods/502

When you click the "update" buttons in MO2, it  only wants to perform updates for Nexus Mods for the game the MO2 instance is for.