Accept/confirm problem for large offers

[NxtChg]

I am having a weird issue with large offers (100+ keys).

 

It seems that Steam takes progressively longer time to accept or confirm an offer.

 

For example, 4 keys take 3 seconds to confirm, 50 keys take 20 seconds, and 100+ just times out after 30 seconds.

 

If the bot receives keys, the time delay happens in 'https://steamcommunity.com/tradeoffer/offerid/accept'and returns error 500 after 30 seconds.

 

When the bot gives keys, the time delay happens in Community.respondToConfirmation() https://steamcommunity.com/mobileconf/ajaxop and returns "success: false" after 30 seconds.

 

What's even weirder is that the next request to fetch active offers is also delayed by about 20 seconds or times out with error 500 too.

 

This doesn't seem like a rate limit issue, as I added generous delays between requests, for example confirming only after 4 seconds. And the delay also clearly depends on the number of items in the offer.

 

confrimationChecker is not active, and all requests are processed strictly sequentially.

 

Anyone experienced such an issue? What could be the problem here? Any ideas?

[Dr. McKay]

This is normal. When a trade is completed, the Steam backend makes two HTTP requests to the item server per item, and those requests aren't quick (something in the ballpark of 500ms per item I think). So if you're doing a really big trade, the request in which it's completed (if the offer recipient is only receiving items, the request to accept the offer, otherwise, the request to confirm it) will timeout after 30 seconds, but the trade will keep committing on the server. And it seems that while a trade is committing the rest of the API gets cranky for your account, probably because it doesn't feel like playing ball while a trade is in progress.

[NxtChg]

Thanks for explaining! This makes a lot of sense now