Error.....Please Fix

[overwatch873]

Binary bot randomly freezes when opening a new trade.....internet connection is perfect....it really annoys since you have to reload the bot page all over again after that....and if you are using martingale.....you wont recover your looses....many people have complained about this issue....but hasnt been really fixed.. @aminmarashi-binary @Mahboobeh-binary

[aaimio]

Hey @overwatch873,

Thanks for letting us know. Would you be able to share your strategy with us so we can investigate where it may go wrong?

Regards,
Aaron

[Kosta92]

This has been going on for years. They won't fix it.

[aaimio]

@Kosta92,

We'd love to fix it, however we need steps to reproduce so we can investigate what's happening here.

Regards,
Aaron

[deny-titan]

@overwatch873 I have the same problem, about 1-2 weeks in deriv (DBot). I guess that binary.com server now is limiting request of transaction with Bot that contain complex calculation and creating a massive journal output. Of course, it be more difficult to create bot. But I have an idea, that every starting bot, it always ask wheater we have a lost condition that require compensation, like martingale money management. If condition is true than bot is restart with little question about common normal stake, martingale level, and amount of compensation. So, the bot restart again 'like resuming' last condition from accidentaly stopped before.

[aaimio]

Hey @deny-titan,

Just a couple questions that'll help us investigate:

• How long do you usually run your bot until it stops working?
• Are you able to share a (modified) strategy with us that will have this behaviour?

Regards,
Aaron

[deny-titan]

Hey @deny-titan,

Just a couple questions that'll help us investigate:

• How long do you usually run your bot until it stops working?
• Are you able to share a (modified) strategy with us that will have this behaviour?

Regards,
Aaron

Ussualy my bot is running about 30-50 minutes. But with the same code, 1-2 weeks later, it stop working randomly about 5-10 minute. But sometimes it can be finished after target profit is reached. For your info, I ran strategy Digit Over/Under and Rise/Fall on Volatile Index market.

Regards,
Deny

[deny-titan]

@aaron-binary I have a question. Is there a limitation in 'time lag' by second(s) that allowing the Bot to send next purchase request to server? For example, if we in Volatile (1s) market, we cannot send a request before 4 seconds for next purchase. Or any other limitation?

Regards,
Deny

[aaimio]

Hey @deny-titan,

Thank you for getting back to me.

Ussualy my bot is running about 30-50 minutes. But with the same code, 1-2 weeks later, it stop working randomly about 5-10 minute. But sometimes it can be finished after target profit is reached. For your info, I ran strategy Digit Over/Under and Rise/Fall on Volatile Index market.

Let me look into this and see if I can reproduce the behaviour.

@aaron-binary I have a question. Is there a limitation in 'time lag' by second(s) that allowing the Bot to send next purchase request to server? For example, if we in Volatile (1s) market, we cannot send a request before 4 seconds for next purchase. Or any other limitation?

The only limitation that we have is that we only allow purchasing a single contract at a time. Only after a contract has been finished another purchase can be made.

Regards,
Aaron

[deny-titan]

@aaron-binary Thanks for your support!

[deny-titan]

@aaron-binary I send you a report according to my explanation few days ago. Here is my screenshot (tonight) of Transaction and Journal condition when it happen. The bot stopped after last trasaction settled. Also I send a simple Bot that may can you use to reproduce this error.

Regards,
Deny

DigitUnder_Error_no_execution_after_win_or_loss.zip

[aaimio]

Hey @deny-titan,

Thank you 🙏 .

This will help us investigate what we can do to ensure your bot keeps running without interruptions.

Regards,
Aaron

[WaliedJackson]

Hi @deny-titan

I am experiencing the exact same issue. At times it will work for 10mins and then the next for 1min or less.

Hope you find a solution. This happens on Live and Demo.

Thanks
Walied

[aaimio]

Hey @WaliedJackson,

We've released some fixes, could you confirm whether this is still happening?

Regards,
Aaron