Bug info: I am having bot error, i have set two paper bots on same binnace exchange , one bot go long with 5x leverage and short bot go short with 10x leverage. When i opened my long bot it was throwing me some error in picture below,
Short doesn’t throw any error, why is that
This is error we get directly from exchange. Did you set hedge mode?
Without hedge mode you cannot have long and short bots at the same time even with equal leverage
Let me check
But lond and short positions doesn’t open at the same time , they happen apart from each other , distance of days
The error in bot means that Binance not allow you to change leverage with active position.
With hedge mode you can have both long and short, no problem.
But how bot can change leverage? It is paper bot , i don’t understand this error, i was going to make it live but now i dont know where is this error coming from
Are there other long deals with different leverage open at your paper account?
Sorry didn’t noticed that it is paper.
I will check it. Meanwhile you can create another account, or set the same leverages for both bots if possible
Yes on the same account there is another long paper bot with different leverage
That’s the issue. The exchange won’t allow it, so Gainium doesn’t allow it neither. You have to use a separate paper account.
I dont understand why exchange wont allow it, as there two seprate bots which works with differene of days
As far as I have read from other users in other chats, no exchange allows to run orders with different leverage for the same pair in the same direction.
You are not getting it, first of all
1, Positions are not going in same directions , one is long and one is short
2, two bots dont open a position at same day , there is days of time difference between two bots
3, when long bot open a long position then short bot is idle and when short bot open a position then long bot is idle.
This shouldn’t happen in theory two bots should open position without any error even with different leverage for same pair when they act at very different time zones
It was fixed, thanks!
