Dr. McKay

loginKeys are irrelevant if you're using a refresh token. If you have a refresh token, always use it.
A refresh token is valid for 200 days, and once it expires you'll need to login again.

This is a JavaScript quirk. You need to do var buyer_add = offer.addTheirItem.bind(offer)

I'm not aware of any limits imposed as a result of making trades too quickly, just limits on how many web requests you can make.

As far as I'm aware, if a trade is rolled back after it's successfully committed, the trade offer stays in the "accepted" state. Really the only way to know a rollback happened is to either check your trade history or check your inventory and notice that items are gone/replaced.

No, the API method called by getExchangeDetails is the only place to get the trade status.

Figure it out, I'm not going to do your job for you. If you're using node-steamcommunity, the requests it's sending are well-formed. If you aren't, then I can't really help you.

loadUserInventory has been deprecated for years. You should be using getUserInventoryContents.

Yes, Steam's rate limiting is more strict now. You need to make fewer requests or use more IPs.

It's definitely stricter, but it seems to be more than 500/day for me.

Yes.

Looks like your assetIds variable contains an array of arrays.

Not yet, but it will.
Maybe this is a little vague, I'll try to rewrite it. This is only talking about a case where you supply a token that wasn't generated using EAuthTokenPlatformType.SteamClient. If the token is invalid for any other reason, you'll get the normal error event with an EResult value (probably InvalidPassword, but I haven't checked).

That will log the IDs of the items before they were traded. To get new asset IDs, use the getExchangeDetails method on the TradeOffer object.

The order of parameters to the getPersonas callback is err, personas. You have it backwards. The getPersonas function accepts multiple IDs. Why are you calling it individually for each ID? You might need to delay some time after calling setPersona to set yourself online, as you're currently sending the getPersonas requests synchronously at the same time as setPersona, without giving Steam enough time to process that you're now online.

Nothing that steam-user does uses the WebAPI. There might be limits on various requests, but the WebAPI limit doesn't apply here.
Using steam-user to listen for the user event doesn't make any requests at all; Steam pushes down profile updates as they happen.

As far as I'm aware, all CS:GO items have a trade cooldown when traded. I don't know why you'd be seeing different behavior.

It's fixed now.

Yes, it's gone.

Yes you are right it appears I have an old version. Installing the newest release fixed the issue

I don't see any reason why that would happen unless you installed a really old version somehow. Could you paste the contents of node_modules/steamcommunity/package.json?

4.24.6 should improve this issue.

Thanks for the quick response! 
Sure, these versions were used the last time the error occurred (2022-07-04):
OS: Arch Linux 5.15.55-1-lts
My bot: BETA 2.12 b8 (Repo at the point of commit)
node.js: 16.13.1
steam-user: 4.24.3
steam-crypto: 1.2.0
steamcommunity: 3.44.1
 
One more interesting thing I just noticed in my log:
There was one time (out of 5 since 2022-05-22) where an account recieved a second different error as well and actually managed to relog fine.
(So 4 times since 2022-05-22 the behaviour above happend, one time this happened)
Log excerpt from connection loss until webSession event:
[2022-05-24 15:37:51 | INFO] [Bot 32] Lost connection to Steam. Reason: Error: Encrypted message authentication failed [2022-05-24 15:37:51 | INFO] [Bot 32] Initiating a relog in 30 seconds. [ERROR] Uncaught Exception Error! Reason: RangeError: Illegal range: 0 <= 8 <= 1208313696 <= 148 at ByteBuffer.module.exports.ByteBufferPrototype.slice (/steam-comment-service-bot/node_modules/bytebuffer/dist/bytebuffer-node.js:2764:23) at SteamUser._handleNetMessage (/steam-comment-service-bot/node_modules/steam-user/components/03-messages.js:529:81) at TCPConnection._readMessage (/steam-comment-service-bot/node_modules/steam-user/components/connection_protocols/tcp.js:194:13) at Socket.emit (node:events:390:28) at emitReadable_ (node:internal/streams/readable:578:12) at onEofChunk (node:internal/streams/readable:556:5) at readableAddChunk (node:internal/streams/readable:269:5) at Socket.Readable.push (node:internal/streams/readable:228:10) at TCP.onStreamRead (node:internal/stream_base_commons:249:12) [2022-05-24 15:37:51 | WARN] If the bot doesn't work correctly anymore after this error then please restart it! [ERROR] Uncaught Exception Error! Reason: Error: error:0606506D:digital envelope routines:EVP_DecryptFinal_ex:wrong final block length at CipherBase.final (<anonymous>) at Decipheriv._flush (node:internal/crypto/cipher:160:29) at Decipheriv.final [as _final] (node:internal/streams/transform:112:25) at callFinal (node:internal/streams/writable:694:27) at prefinish (node:internal/streams/writable:719:7) at finishMaybe (node:internal/streams/writable:729:5) at Decipheriv.Writable.end (node:internal/streams/writable:631:5) at Object.exports.symmetricDecrypt (/steam-comment-service-bot/node_modules/@doctormckay/steam-crypto/index.js:80:10) at TCPConnection._readMessage (/steam-comment-service-bot/node_modules/steam-user/components/connection_protocols/tcp.js:185:27) at Socket.emit (node:events:390:28) [2022-05-24 15:37:51 | WARN] If the bot doesn't work correctly anymore after this error then please restart it! [2022-05-24 15:38:21 | INFO] [Bot 32] Queueing for a relog. 0 other accounts are waiting... [2022-05-24 15:38:22 | INFO] [Bot 32] It is now my turn. Waiting 2.5 seconds before attempting to relog... [2022-05-24 15:38:25 | INFO] [Bot 32] Trying to relog with proxy 5... [2022-05-24 15:38:26 | INFO] [Bot 32] Account logged in! Waiting for websession... [2022-05-24 15:38:27 | INFO] [Bot 32] Got websession and set cookies. [2022-05-24 15:38:27 | INFO] [Bot 32] Relog successful. [2022-05-24 15:38:27 | INFO] [Bot 32] Accepting offline friend & group invites... Maybe this helps in some way narrowing down the issue.

I'll try and force the protocol to WebSocket in the meantime as you suggested, however it's hard to see if it'll make a difference as the behaviour only occurrs roughly once a month.

I can see it right there.

Update the module to the latest version.
 

Depends on why you're not connected. If you disconnected because Steam went down or you otherwise lost connection, SteamUser will automatically attempt to reconnect. Unless you messed with the autoRelogin option, the only situation where you'd need to call logOn again is if the error event got emitted.