search

nothingisdead / npm-kraken-api

[DEPRECATED] NodeJS Client Library for the Kraken (kraken.com) API
Other
412 stars 188 forks source link

Request times out but order is posted #37

Open aastein opened 7 years ago

aastein commented 7 years ago

Posted a sell market order and the order went through but the request timed out. I'm gonna submit a PR to increase the default timeout :)

aastein commented 7 years ago

38

ekr3peeK commented 7 years ago

Maybe this is not the right place to post this, as I am using the PHP api for Kraken, but as this git is not dead, as the PHP version, I try to raise awareness here, maybe someone smarter then me, can come up with a solution.

The problem is simmilar to the one described above, but instead of curl timeouts, I am receiving sometimes HTML data from the api, the annoying Cloudflare notification about not reaching the Kraken website. The problem is, that this result has nothing to do with the timeouts, yet the orders somehow are still processed by Kraken. I've already got a workaround for this, by using the user added references when creating a new trade order, and verifying if the reference exists, before trying to create a new one, but there is no user reference possibility for withdrawals unfortunatly, so there is no surefire way to verify, if the withdrawal request was indeed processed by Kraken or not.

Anyone experiencing these same issues while using this API? Any ideas about this? Krakens services are very bad lately, usually returning cloudflare messages every 5-6th request I made.

kroitor commented 7 years ago

@ekr3peeK, don't know how to help solving this, just wanted to confirm, that we observe same issues with the quality of service from Kraken. We encountered numerous [EService:Unavailable], request timeouts, Cloudflare "website-unreachable" error responses, all of that.

But the user ref id workaround does not help in our case, because their orders API shows significant time lags when Kraken is under peak loads. For example, most often an attempt to open an order fails with an unknown result, due to the nature of the above errors. We have to double-check if it exists in our orders after receiving an ambiguous "no reply". If we query our orders for that user ref id after the failed attempt, the order in question is not reported by their open/closed orders API. And then it reappears in ledgers 5-10 minutes later, surprise-surprise! This means inconsistency of their internals, and it kinda kills the trade.

Kraken:

Please double check if an order is submitted (sometimes it takes a few minutes for the order to appear in the orders list)

↑ from here: https://support.kraken.com/hc/en-us/articles/115014409247-Order-may-have-failed-EService-Unavailable

ekr3peeK commented 7 years ago

@kroitor I have to laugh at the "We are well aware of this issue and resolving it is our team's top priority.". I am using this API for 2 months now, and since the beginning this problem is present, yet a team of the size of Kraken, couldn't solve this issue since then, when this is their TOP priority.

I will have to look quick for some other alternatives, because Kraken is useless this way for anything serious IMO:(