Binary-bot: Bot Error

[Boomandree]

Hello!
I wanted to know why the binary bot doesn´t restart trading after the error "the price moved too much"?
Is there a solution that the bot trade further even with higher stake after losing?

Thank you

[aminmarashi-binary]

Hi,

Have you tried this?

[Boomandree]

Yes, I´m using that. There is also the restart message, but after the countdown the bot stops trading. A few days ago it restarted after this error.

thank you

[Boomandree]

Hello!
Should I do something or who is solving this bug?

Thank you

[aminmarashi-binary]

Will look into it.

[aminmarashi-binary]

Kind of hard to reproduce, but I believe #90 will fix this problem too.
If you have blocks that can be used to reproduce this issue easily could you please share it with me?

[Boomandree]

Hello!
I would like to send it by email. Tell me Email adress.

[aminmarashi-binary]

Please send your email to [email protected], Please include Bot Error #158 in your email subject.

[aminmarashi-binary]

Thanks, I received the file.

[Boomandree]

Hello!
What about the issue, can you fix it?

Thank you

[aminmarashi-binary]

In order to fix this issue and have a more reliable restart (or maybe pause/resume) functionality, we need #90 to be done. Please be patient and rest assured that we're looking into fixing this.

[Andreas2017]

Since this week the problem is also at beta robot. The bots are unusable when i must restart manually. It just happens too often that the market moves too much. Please change the settings back so that one bot is usable. Do have a solution? I appreciate your work and the approach of the of the Bots are very good! ;) Thanks for your answer. Best, ...

[aminmarashi-binary]

I'm truly sorry for the inconvenience caused. We're refactoring the code completely and will eventually remove Restart On Error option.
I hope we release a beta version soon so that you'll be able to start using it asap.
The beta version hopefully will not stop trading at any point by any error, therefore there will be no need to restart the trade.

[Boomandree]

Hello!
That would be great.
Thank you.

[aminmarashi-binary]

Good news: the implementation is done. We will release the new version in beta soon (after thoroughly testing).

[Andreas2017]

Nice! Give a sign after the testing. Thanks!

[aminmarashi-binary]

You can start experimenting with the future release in here.
If nothing goes wrong we're going to release it.
Hopefully you won't need the restart on error option anymore.

[okovalov]

@aminmarashi by any chance does your bot on github.io have https://github.com/binary-com/binary-bot/issues/152 implemented? cant wait for this feature to be developed.. would be so nice to have it ! a lot of bots ideas are blocked by that issue... :(

[aminmarashi-binary]

152 is implemented under the hood and Binary Bot CLI supports it. You can install Binary Bot CLI and start using the feature. It's not well documented yet, but if you can't wait, you can tell me about your strategy I will write a code and give it to you to run using the command-line interface.

I recommend you to wait, cause I hope I can get it done until the end of the week.

[okovalov]

@aminmarashi oh sure! end of the week is totally fine! But the thing is I was not even aware the cli things exists! that is so cool! I would definitely give it a try! I am sure that is 100 times more flexible comparing to the visual builder. by any chance do you have bot-example.js somewhere in the gist? just wanted to take a look at it! I am sure I am gonna love it.. the beauty of node.js + socket.io is not even CLOSE performance wise to browser tab eating all the resources and becoming a leaking monster in a few hours..

[aminmarashi-binary]

Cool, I'm glad that you're interested. It's a work-in-progress, but you can find an example here
Edit: I updated the above link, you can find the current source here

[okovalov]

@aminmarashi nice. so I assume there's a watch for 'after' and I can easily navigate into the package source to see what else methods are available for Bot (like isSellAvailable etc) thank you!

[aminmarashi-binary]

Sure, there are actually two watches only one for before the other one for during. Simply everything before watch('before') corresponds to block #1 and everything after watch('during') corresponds to block #4
Any help or suggestion about how to make the API better is highly appreciated.

Bot.start(...) // (1) trade definitions
while(watch('before')) {
 // (2) before purchase
 Bot.purchase('CALL') // Purchase
}
while(watch('during')) {
 // (3) during a purchased contract
}
// (4) after contract is finished

[okovalov]

@aminmarashi gotcha.. so that's why overwriting last digit prediction would work on cli - basically if that variable is in a top context, (global one) then we can overwrite it from anywhere (either from 'during' or form 'before' and ofcourse after contract is finished we can also overwrite it, simply because it is a global one..

[Andreas2017]

"You can start experimenting with the future release in here.
If nothing goes wrong we're going to release it.
Hopefully you won't need the restart on error option anymore."

Same Problem when the underlying market move too much.
Settings are: EUR/USD, Candle Interval: 1 min, Duration 5-10 Ticks
I need a restart on error option. ;) It is better when the market is not so volatile but in the prime time it comes very often. Best

[Andreas2017]

Here is a picture from my Bot.

[aminmarashi-binary]

@Andreas2017 Too bad, what kind of error did you get? Cause the restart option is there, only behind the scenes and only for the smallest steps possible, therefore it should be a safe restart now which means you don't have to worry about the variables changed from the last iteration and so on.
I hope we don't have to bring the restart function back, so I'll need your help to figure out the source of errors.
the tests you make for the error handling should be only dependent on the first block. So could you please take a screenshot of the first block and send it here?
Ok I saw the issue myself and working to fix it.

[aminmarashi-binary]

@Andreas2017
I appreciate your report, could you please try again with the latest version?
I really have high hopes that you won't see the same error this time.

[Andreas2017]

@aminmarashi I have tested your latest version. My bot which i have posted 6 day ago works fine but other bots with other indicators have problems. For example Bollinger Bands doesn't work right.

As you can see in the results, Trade 11 comes 5 times.

Sometimes stops the bot without any reason / error? The stop / play button don`t change.

[aminmarashi-binary]

@Andreas2017 Thanks for reporting those bugs (#197 and #196).
The trade 11 is actually both trade 11 and 12, it happens when two bots are working at the same time (#196).
I'll investigate the bot stopping, and make sure it does not stop unless there's a good reason.

[Andreas2017]

Bots.zip

This bots don't work :( The bot "Bot EMA 9.xml" is a EUR/USD 1min on 1min Bot. After a couple trades it comes a trade that never ends and runs and runs. In this case no other trade can start and the bot "hangs".

[aminmarashi-binary]

Thanks for reporting another important issue @Andreas2017. Will be fixed soon.

[aminmarashi-binary]

@Andreas2017 Thanks to your report I improved the error handling of open contracts and hopefully, the mentioned problem won't happen again.

[Fruitfella]

hi amin.
about this "the price moved too much" error, its not only happen when opening a trade (which fail and the bot stop) but also when closing a trade, and its really awful because i lost money (the stake) even though it should be a winning trade.

about the "restart on error" checkbox, i wonder if it didnt work on martingale strategy because we need to input profit, loss and stake amount (input dialogue box) when the bot start. so if we dont use input dialogue box instead use the input on blocks will this checkbox work? i cant try it because i dont understand programming, so i can only ask.

ps: sorry for my bad english.

[aminmarashi-binary]

Sorry for the inconvenience caused @Fruitfella. We're working on fixing this problem. Unfortunately is a little bit more complicated that we anticipated. But I really hope we can release the fixed version very soon.
Meanwhile it would be more than helpful for us if you could check your strategy in our experimental version which we constantly work on to make better, and let us know if you faced any problems.

[Fruitfella]

hi amin,
ive tested my strategy on experimental version. just for an hour though, cuz im busy these days.
there was no "the price moved too much" error so far, so idk regarding this problem. but i got problem with martingale.

idk programming so idk how to fix it.
do you have martingale xml that work on experimental version?

ps: my martingale works well on bot.binary.com
pps: again, sorry for the terrible english.

[aminmarashi-binary]

@Fruitfella The issue is now fixed. Many thanks for pointing it out.

[Fruitfella]

Hello..
theres seem no more "the price moved too much" error. but..
i got this "rate limit" error instead

its kill the bot, afterward the bot tried to resurrect but failed

it said "undefined is not function", i dont even know what its talking about.

also after a few trades my bot didnt purchase anything even though the conditions are met, i wait for few minutes but still no trade again. the bot still running. so i stop it and then start it again and its work. but after a few trades it didnt purchase anything again.

[aminmarashi-binary]

@Fruitfella What strategy is that?

[Fruitfella]

though i dont know programming, the jigsaw make it easy to build my own bot and its fun.
i made modified pinbar using some bot samples, mixed it with my own action price scenario for purchase.
i use martingale on loss and semi martingale on win (only double it a few times then return it to initial stake, in this bot i only double it after 1 win [the one with initial stake. i dont double the win after loss], 3 consecutive wins, 5,7, and so on)

my bot did well on official version except for that "price move to much" error, i mean its always purchase when the condition met.
but dont know why with the experimental version it didnt make any purchase after a few trades, and that "rate limit" error kill the martingale just like the official version's "price move to much" did.

you can see it at the pict on my previous comment, at trade 50 it stopped, i started it again and got a winning trade at 52 i should get my losses back if the martingale work. and its stopped again at 53.
and the purchase problem happen after that.

on some occasions after the bot killed by the error, i start it again and it did 2 trades at every purchase but only 1 trade got closed/finished/paid, it keep doing so until i stop it and start it again. i lost the snapshot of this error (accidentally delete), so i cant show it to you.

also, i tried my bot on volatility indices (official), it did very well, no error even after 5 hours, too bad i didnt get profit but get massive loss, though its demo account i feel downhearted and felt wronged by my own bot. lol
btw the strategy itself is not that bad on forex.

I hope i can really be a help to you.
best regards.

ps : sorry for my terrible english.

[aminmarashi-binary]

I couldn't find the error message in our logs. Could you please send us your strategy file [email protected]?

[Fruitfella]

sure

[Fruitfella]

i tested my newer ver bot on official binarybot. i made it for volatility indices since forex has that error.
it did better than the prev ver.
i tested it for 4+ hours (i leave it and go to sleep), 110wins/108loss, no error and got some profit thanks to martingale.
then i tested it on experimental binarybot and this hapen :
no error message this time but again, its didnt purchase anymore after few trades (trade 5)

i stop the bot and check the blocks, seems it fail to load some pieces (duration and stake), its funny since the bot still manage to make few trade with the right duration and stake amount, and the martingale works too. i wonder if its fail to load another blocks or scripts and thats why this problem occur.

i start it again after place the missing duration and stake pieces, and that problem still happen (trade 8)

i just notice that the candle didnt move, it didnt show the new candle as it should even after few minutes passed. i click ">" button and its didnt works, only after i click "-" (zoom out) it did show the newest candle.

btw, what is this?

Ps: i assemble my bot on official binarybot.
i think this experimental binarybot has more problems than the official.

[Fruitfella]

about the chart, the official binarybot also same. it didnt show (auto scroll) the new candle.
i cant remember when the last time i saw it scrolling automatically.
also, after i tested my bot on experimentalbot, i load it to officialbot, many blocks are missing. seems like it disappear when i load it on experimentalbot. compatibility issue?

[delonbh]

About that black square, delete it, and Savé BOT with an sufixo like
botX-betaserver.xml.
Open it again and try.
Got the same problem and fixed doing that. Maybe a compatibility issue by
running officila xml in beta.

Em 3 de mai de 2017 07:09, "Fruitfella" [e-mail] escreveu:

i tested my newer ver bot on official binarybot. i made it for volatility
indices since forex has that error.
it did better than the prev ver.
i tested it for 4+ hours (i leave it and go to sleep), 110wins/108loss, no
error and got some profit thanks to martingale.
then i tested it on experimental binarybot and this hapen :
no error message this time but again, its didnt purchase anymore after few
trades (trade 5)
[image: capture 16]
https://cloud.githubusercontent.com/assets/26277327/25655924/00fda086-3021-11e7-8e0f-378cf44c31e9.PNG

i stop the bot and check the blocks, seems it fail to load some pieces
(duration and stake), its funny since the bot still manage to make few
trade with the right duration and stake amount, and the martingale works
too. i wonder if its fail to load another blocks or scripts and thats why
this problem occur.
[image: capture 13]
https://cloud.githubusercontent.com/assets/26277327/25656245/4d11582c-3022-11e7-8224-898d010f28e2.PNG

i start it again after place the missing duration and stake pieces, and
that problem still happen (trade 8)
[image: capture 17]
https://cloud.githubusercontent.com/assets/26277327/25656350/d76484b8-3022-11e7-9d04-2994b6dd21ca.PNG

i just notice that the candle didnt move, it didnt show the new candle as
it should even after few minutes passed. i click ">" button and its didnt
works, only after i click "-" (zoom out) it did show the newest candle.

btw, what is this?
[image: capture 18]
https://cloud.githubusercontent.com/assets/26277327/25656444/3caaab72-3023-11e7-8554-7d97412df830.PNG

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/binary-com/binary-bot/issues/158#issuecomment-298871287,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYhTBw21hLB_9-BnGMOLSn-SFVrQA1Vqks5r2FJYgaJpZM4L9XBK
.

[Fruitfella]

thanks delon.
i think ill just test my bot on official at the moment.

btw about that "the price moved too much" error on the official, i thought these.

1. after that error kill the bot, we can click that start button and the bot lives again. so if after the bot dead you make it automatically execute that "start" command under that button, wont that problem solve?
   seems like the idea of that "restart on error" checkbox is that, but why it didnt works like when you click the button?
2. the problem getting worse on martingale strategy, it simply burn our money out.
   but if its possible for the bot to read the trading record, the problem can be solve with a few tricks.
   by knowing the stake amount and win/loss of the last trade, we can continue the martingale step.
3. if the bot cant read the trading record, i wonder if its possible to save data somewhere so that the bot can use it after we restart it? what about the blocks?
   
   is it possible for the bot to write something on these blocks? i see that the data i input to those block didnt gone even after the bot dead.

ps: as i write this i notice that the chart scrolling works again, its now autoscroll every new candle.

[aminmarashi-binary]

The experimental version is backward compatible, which means you should be able to load your previous blocks in it, but there's no way you can run the blocks created in the experimental version in the official version (no forward compatibility).
PS. Binary Bot does not care about the filenames, as long as it's an xml file downloaded from the binary bot itself it should work fine.

[aminmarashi-binary]

@Fruitfella You're right, that's what the restart button do. the experimental version is essentially the same, but the difference is it does it intelligently so that in the bot point of view it seems like the error never happened.
Assume you have a martingale strategy:

1. you win -> same amount
2. you lost but there was an error so we restart with the same amount
3. the martingale continues

This way you will never be able to compensate the loss amount.
The experimental version is there to fix this issue, after we successfully deployed it, strategies should work as if there was no error.
This is a very complex task and requires lots of work and testing (we basically rewrote the core functionality to achieve this).

I'll look into fixing the block problem, thanks again for pointing it out.

[aminmarashi-binary]

@Fruitfella Fixed the problem with the Exponential Moving Average (EMA) block which was missing. also found the cause of stopping the Bot in the experimental version.
Your strategy was purchasing twice in the 2nd block if certain conditions were met. now it just ignores your second purchase. just refresh and give it a try.
P.S. Great job on the strategy. I really like the way you combined different blocks to build your own strategy.

[Fruitfella]

haha, thanks.
i still perfecting it. not to make it a perfect bot. rather want to make it exactly like what i thought.
my lack in programming language really give me a hard time.
btw, there are some pieces that i dont know what and how to use it such as Loops, Since epoch, random fraction, etc. it would be great if you could make some explanation and examples of using every jigsaw pieces available there.

[okovalov]

Amin , have you updated the core of an npm package as well? I actually
found some bugs there, so will open a few issues tomorrow..

On Wed, May 3, 2017 at 11:33 PM, Fruitfella [e-mail]
wrote:

haha, thanks.
i still perfecting it. not to make it a perfect bot. rather want to make
it exactly like what i thought.
my lack in programming language really give me a hard time.
btw, there are some pieces that i dont know what and how to use it such as
Loops, Since epoch, random fraction, etc. it would be great if you could
make some explanation and examples of using every jigsaw pieces available
there.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/binary-com/binary-bot/issues/158#issuecomment-299089907,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABoK_YE5gPK098g2eO1oxqoVJKeulcM9ks5r2UbxgaJpZM4L9XBK
.

--
"Success is simple. Do what's right, the right way, at the right time."

best regards,
tradakad

[aminmarashi-binary]

Of course, the latest version is 8.0.45, check with bot -V, update with sudo npm i -g binary-bot

[Andreas2017]

@aminmarashi "Fixed the problem with the Exponential Moving Average (EMA) block which was missing. also found the cause of stopping the Bot in the experimental version.
Your strategy was purchasing twice in the 2nd block if certain conditions were met. now it just ignores your second purchase. just refresh and give it a try."

I think it is not fixed. ;) Best

[aminmarashi-binary]

@Andreas2017 Could you please send me your strategy file? You can make a zip file and upload it here.

[Andreas2017]

Bot EMA 9 MG.xml.zip

[aminmarashi-binary]

@Andreas2017 thanks, Did you try refreshing once again? I have no luck reproducing the same issue you had for more than 100 trades. I'm still investigating.

[Andreas2017]

@aminmarashi I run the bot while the central europe time. Means when the German Market is open and much people trading (much volume is in the market). In the night it never happened.

[Fruitfella]

@aminmarashi When an error occur the bot restart after 1.5s, but sometimes after i wait for few seconds its still didnt make any trade so i thought it fail to restart, therefore i click the start button (triangle) and it make trades but purchase twice in every condition met. this double purchases problem didnt always happen though, its hapen sometimes.
i think that happen because actually it didnt fail to restart but due to some reason its lagging. and because i click that triangle, it makes 2 robot running at the same time.
i dont know whether this theory is true, but you should make a notification when the bot succesfuly restart and change that triangle to square.
p.s. i think you should put the "restart on error" checkbox back. i sometimes dont want it to auto restart on error. maybe others too.

[aminmarashi-binary]

@Fruitfella @Andreas2017 I fixed a bug in the code which might be related to your explanations.
The most recent code is deployed to https://bot.binary.com/beta/bot.html.
We added infinite scrolling for trade info and notification log

So now you can clearly see what happened since you started the bot.
I really hope I don't have to bring the restart on error button, because we should handle all recoverable errors in the code, and if the error is not recoverable we should stop the bot and ask the user to take actions.
Though we really care about correctness of binary bot more than anything, and restarting the bot simply doesn't always give us a correct result, we will bring it back and extremely recommend not to use it.
P.S. If you find any error in the beta version please report it here, as we're releasing it soon.

[aminmarashi-binary]

@okovalov You should also update to [email protected]

[okovalov-commer]

@aminmarashi thank you for the headsup! ive seen bunch of commits and had a feeling it would be a good idea to pull the latest version, so again - thank you! will do.

[Fruitfella]

thanks @aminmarashi
btw, could u add sound notification before release the beta?
and time block, i have the need for a block that can tell us the
current time and make trades in a certain hour.
for example if i want to trade only at 08.00am to 11.00am and trade
again at 02.00pm to 05.00pm.

i tried to use candle values open time and seconds since epoch, but
cant see which one is the hour, minute and second in the 10 digits.

On 6/16/17, Oleksandr Kovalov [e-mail] wrote:

@aminmarashi thank you for the headsup! ive seen bunch of commits and had a
feeling it would be a good idea to pull the latest version, so again - thank
you! will do.

--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/binary-com/binary-bot/issues/158#issuecomment-308936714

[aminmarashi-binary]

It's already achievable using epoch time, take a look at https://www.epochconverter.com/.

You can use seconds since epoch block to compare the time you want to trade with the current time.
To compare certain times of the day you can calculate the remainder of epoch by 86400 (which is the number of seconds in 24 hours).

E.g. for your times above you can do:

1. Convert 8 AM of any day to epoch (I used today 8 AM (GMT), you should use 8 AM in your own timezone and recalculate: 1497859200)
   To convert your timezone to GMT you can google: 8am [put your country name here] time to GMT
2. above value (1497859200) % 86400 = 28800
3. Do the same thing for 10 AM: 36000 (notice that it's the same if you add 7200 seconds to the above time ((36000 - 28800) / 3600 = 2))
4. check if seconds since epoch % 86400 is between 28800 and 36000

Note: Dealing with time and date you need to be careful about your timezone, but there's no timezone defined for epoch, so if you could calculate your epoch time correctly you can use it regardless of your timezone.

[Fruitfella]

ah I got it! thanks amin.
i tested my strategy on beta for an hour and its good, its still run
smoothly after error notifications and didnt interupt martingale
strategy, really nice! this issue is solved!
the log is good, the unlimited scroll on trades record also good, but
sometime when I closed the summary pop-up and open it again, the
trades record disappear, its appear again after the bot make a
purchase though.

btw the sound notification is okay right? I think u should add it
before beta release, its very useful especially when testing a
strategy and we cant watch the screen all the time coz we want to make
a cup of coffee or some snacks. ^-^

On 6/19/17, Amin Marashi [e-mail] wrote:

It's already achievable using epoch time, take a look at
https://www.epochconverter.com/.
src="https://user-images.githubusercontent.com/6560964/27266185-4e6b855c-54d1-11e7-82d8-f094f45f4474.png">
You can use seconds since epoch block to compare the time you want to
trade with the current time.
To compare certain times of the day you can calculate the remainder of epoch
by 86400 (which is the number of seconds in 24 hours).

E.g. for your times above you can do:

1. Convert 8 AM of any day to epoch (I used today 8 AM (GMT), you should use
   8 AM in your own timezone and recalculate: 1497859200)
   To convert your timezone to GMT you can google: 8am [put your country name here] time to GMT
2. above value (1497859200) % 86400 = 28800
3. Do the same thing for 10 AM: 36000 (notice that it's the same if you
   add 7200 seconds to the above time ((36000 - 28800) / 3600 = 2))
4. check if seconds since epoch % 86400 is between 28800 and 36000

Note: Dealing with time and date you need to be careful about your timezone,
but there's no timezone defined for epoch, so if you could calculate your
epoch time correctly you can use it regardless of your timezone.
src="https://user-images.githubusercontent.com/6560964/27266637-46ec727e-54d5-11e7-8cc1-7f59bd775aaa.png">

--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/binary-com/binary-bot/issues/158#issuecomment-309320455

[aminmarashi-binary]

Thanks @Fruitfella for reporting the issue with the panel. We did some new release to fix that, you can refresh the beta page to see the newest version. We will definitely add the sound notification as well.

[Fruitfella]

yep, its fixed. thumbs up
theres another problem.
on long expanded block that some part of it are above or below the
page so i need to scroll/move the workspace (by hold-click on empty
workspace then drag) to see it, some part will disappear (crop), it
appear again after i release the mouse though.
its not a big deal and doesnt affect the bot, and i collapse almost
all of my blocks when i dont work(assemble) on it, it just a bit
annoying.

i got a hard time to describe it in english lol, i hope it wont confuse u

[aminmarashi-binary]

Thanks @Fruitfella for the heads up. The issue you mentioned was fixed.

[Fruitfella]

i got new error on my testing, "unknown contract proposal", it stopped the bot.
on first run

i restart it again and its work, but after few trades it stopped again.

idk whats the cause, i'll test it on official to see if i'll get the same error

[Fruitfella]

tested it for 3 hours, 70 trades on official and no "unknown contract proposal" error.
so yep, its not my bots mistake.

[aminmarashi-binary]

@Fruitfella thanks for testing it. Seems like we have to bring the restart option back. Please be patient till we find the least destructive way to do it.

[aminmarashi-binary]

@Fruitfella we added the restart functionality back, but this time more carefully. Please test it and let us know your opinion.
@okovalov in version 8.1.1 now binary bot supports shouldRestartOnError in Bot.init
example:

Bot.init(token, {
    shouldRestartOnError: true,
    ...
});

[Fruitfella]

@aminmarashi after an hour it didnt purchase anything not even once while it did few times on official

[okovalov]

@aminmarashi thank you. have it updated

[Fruitfella]

@aminmarashi i checked the problem with few experiments and found the cause.
[this block is called on every tick] run twice on every tick now, it screw my bot's logic, thats why my bot didnt works well now. it was fine yesterday before the 'restart' came back.
please make it run just once on every tick like before.

thanks

[aminmarashi-binary]

I'll look into fixing it @Fruitfella. Btw, was the restart because of the same error (unknown contract proposal)?

[aminmarashi-binary]

@Fruitfella could you please check with the latest version?

[Fruitfella]

[this block is called on every tick] issue fixed, as for restart idk. i dont get "unknown contract proposal" error anymore and that is better haha. ill see if this will continue without that error occur till tomorrow.

[Fruitfella]

Still dont get that "unknown contract proposal" so cant say anything about the restart.
Its good though, since i also never get that error on official version 👍

[aminmarashi-binary]

We released the beta version today, after 100,000 successful trades.

[Andreas2017]

Hi, good work so far but after the restart functionality is back i have the feeling that the bot is lagging and sometimes he freezes for a while until he goes on.

[aminmarashi-binary]

Lagging can be the result of many things, e.g. errors in our backend which Binary Bot tries to recover from automatically in the background, reaching limits, network lags, etc.
@Andreas2017 Which market and trade type are you trying with?

[Andreas2017]

@aminmarashi Thank you for your help! Here is the bot... ;)

Bollinger und RSI change by loss 1.3.xml.zip

Chrome says that the site don't reacts.

[aminmarashi-binary]

@Andreas2017 I added a switch for restarting sell/buy requests. If you unselect the feature you'll get a better performance.
But be careful because the errors happening during buy/sell requests won't be captured and if you don't select the restart trade flag either your bot will stop.
Restarting the trade means forgetting about any changes you made after the last trade started and before the error happened. So you have to be extra careful using restart last trade on error feature.

Imagine you successfully purchased a contract which you want to sell at market. If selling at market fails and restart buy/sell is not selected but restart trade is selected we restart the trade without waiting for the last purchased contract to finish.

Try this (with virtual account) and you'll know what I mean:

[Andreas2017]

@aminmarashi Nice, it works for me so far. But can it be that the "bot ignores the unsuccessful trade" switch don't work?

[aminmarashi-binary]

Do you mean it stopped trading?

[Andreas2017]

@aminmarashi Yes, the bot stops after an unsuccessful trade. You can it see in my last picture.

[aminmarashi-binary]

@Andreas2017 Sorry for the inconvenience. We're trying to fix this: https://github.com/binary-com/binary-bot/issues/305

[thorik1001]

Dearest All,

How to enter transaction for highest digit Only and repeat until WON.
and.. if WON .. calculating again to find highest digit again...and repeat until WON.
and..and..and...

file change txt to xml.
DM-BOT-NEW.txt

[webogist]

Someone please help ME!!! I want an adjustment to my bot, I want the LDP(last digit prediction) to change value(numbers) after every win in digit differs.
What varibales do i add to pls. i alreay have the LDP sent to random. but not changing at every win, i will have to stop and staert again before the prediction changes. Pls help me with what to do to autmate this process.
Thanks

[JGihon]

Hello Aminmarashi,

As I am scanning through the topics to find a solution for my issue (https://github.com/binary-com/binary-bot/issues/710) I have read this one above.

When the bot opens multiple positions one after another based on error and restart that's really an unpleasant situation, so how about you build a function which sells all positions at market like an emergency switch if such errors occur? For example: if bot stops during trade (which happens to me often) that means trade management function is dead, sell at market is not functional then error message sent and emergency switch is triggered if enabled, that is all open positions are to be sold at market.

I think it would be appreciated a lot by traders.

Thanks,
Gihon

[Shinobot]

Good friends, someone could help me in how to get a martingar to a robot please help

[JGihon]

Hello Shinobot,
Have you got a solution yet?
If you need help maybe I can assist you.
[email protected]

[JGihon]

Hello Webogist,
Do you still need help?

[esperanda01]

Please this issue that's stops the bot with a reason that "the market moved too much " is really bad and continues up till now. Is there a way out ? And is any any other automation aside the xml bot ?

[gizzsnallu]

hii everyone... i have edited a bot but its not running it shows please enter positive number... and i made a bot which contains two barrier offset for over and under.. while running bot its running only one barrier offset... i need that barrier offset should work on both over and under trades..

[gizzsnallu]

please can anyone help...