JamesRook Posted February 17, 2023 Share Posted February 17, 2023 When I start Vortex it throws a "Failed to get collections list" error. I haven't used collections yet although I did DL a basic Skyrim collection just to see if the error would go away. Scary that it tried to install after I checked Install Later. Is there a setting I have to change? I might want to use Collections at in the future, but not now. Link to comment Share on other sites More sharing options...
Azerkeux Posted February 17, 2023 Share Posted February 17, 2023 I am experiencing the exact same error code- have never used collections at all and not sure how to address this Link to comment Share on other sites More sharing options...
AugustaCalidia Posted February 17, 2023 Share Posted February 17, 2023 The same error pops up for me. I've never downloaded a collection. Here's the relevant error information found in the Vortex log. code: undefinedField, message=Error: Field 'currentRevision' doesn't exist on type 'Collection' at Proxy.genError (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\@nexusmods\nexus-api\lib\Nexus.js:853:20) at Proxy.<anonymous> (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\@nexusmods\nexus-api\lib\Nexus.js:875:28) at Generator.next (<anonymous>) at fulfilled (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\@nexusmods\nexus-api\lib\Nexus.js:5:58) at tryCatcher (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23) at Promise._settlePromiseFromHandler (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:547:31) at Promise._settlePromise (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18) at Promise._settlePromise0 (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:649:10) at Promise._settlePromises (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:729:18) at _drainQueueStep (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:93:12) at _drainQueue (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:86:9) at Async._drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:102:5) at Async.drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:15:14) at process.processTicksAndRejections (node:internal/process/task_queues:96:5) Link to comment Share on other sites More sharing options...
Solution Deleted6174501User Posted February 17, 2023 Solution Share Posted February 17, 2023 (edited) I can reproduce if not logged in, then log in (vortex). Selecting X removes error warning & doesn't recur until logged out/back in again. Disabling Collection extension in Extension tab prior to logging in suppresses error message. Edited February 17, 2023 by Guest Link to comment Share on other sites More sharing options...
AugustaCalidia Posted February 17, 2023 Share Posted February 17, 2023 I can reproduce if not logged in, then log in (vortex). Selecting X removes error warning & doesn't recur until logged out/back in again. Disabling Collection extension in Extension tab prior to logging in suppresses error message. Thank you for the tip. I disabled the Collections extension, and now everything is OK. Link to comment Share on other sites More sharing options...
rmm200 Posted February 17, 2023 Share Posted February 17, 2023 (edited) This is the place to come! I got bitten with the same irritating error. And now - all quiet on the Western front. Thanks! Edited February 17, 2023 by rmm200 Link to comment Share on other sites More sharing options...
JamesRook Posted February 17, 2023 Author Share Posted February 17, 2023 Big thanks to Cragslist for the solution. Worked great. Link to comment Share on other sites More sharing options...
Deleted6174501User Posted February 18, 2023 Share Posted February 18, 2023 Hopefully, dismissing (or suppressing) it as a benign error is only a temporary measure. Link to comment Share on other sites More sharing options...
LsChlong69 Posted February 18, 2023 Share Posted February 18, 2023 Same thing is happening to me except manage rules button is gone!! Link to comment Share on other sites More sharing options...
DOVAHKI1N Posted February 18, 2023 Share Posted February 18, 2023 Just started getting this error after the latest update. Thank you for the fix, Cragslist! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now