Bug fixing project on existing tool (problem solver needed): Feature of auto-closing Stop Pending position(s)

Price of this bug fixing project can be little negotiated further. Please read the following text entirely.

I am looking for expert with experiences in the most complex possible bugs (technical problems) in existing tool for MT4. Someone, who perfectly understands that development code needs to be understood in smallest possible details before 100% correct decision can be done: Which small piece of the entire development code is related to particular single feature, out of A LOT of other features. which is a subject of a bug as it doesn't work exactly how I want.

So I would need bugs solving expert who really has surgical accuracy when it comes to being 100% sure that correct part of the code is related to the feature causing the problem. What I am the most worried for is that you would edit something what is unrelated to particular feature with problem (bug). There are so many features. So again: kindly take care that you track correct relevant piece of development code which I will send to you if you decide to contact me.

I have permission from the developer to share this entire development code with expert who will be willing to check the problem. Developer who created that tool for me spent over half YEAR working on just this single problematic feature with many different approaches but neither of them guaranteed 100% of times work. I (via my testing), as the end user as well as developer made the accuracy of the feature to around 99.99%, sometimes even 99.999%. However, I would really need that feature works 100% of times guaranteed. So there may be needed a bit different approach, perhaps some piece of programming line differently created. The developer is extremely professional, highly experienced, delivers best possible quality and it is great to using his development service. However, my requirement in particular problematic feature is very high: That single problematic feature (all others features are working good!!!) and its performance shall be considered as one of the most complex bugs in the history of MT4 so please be prepared for extremely complex situation and probably also hard to be tracked in the code - which exact piece of the entire development code is related to this ONE (1) single problematic feature.

Extremely brief description of entire tool is the following (I said extremely brief because I could have written a book about it): I search for single currency which can be either on the left or on the right side of currency pair symbols. Single currencies like btc, xau,... are considered as currency pairs too and some currency pair may have or may not have additional symbols of characters in the title of the trading symbol (e.g. ABC/DEF or ABCDEFpro,...). Tool goes through entire Marketwatch and provides list of currency pairs (single currency either on left or right side of symbol title). I also get information like minimum buy stop distance, minimum sell stop distance, take profit price per point based on my user input on amount of money <currency on trading account is automatically recognized>, stop loss price per point based on my user input on amount of money <currency on trading account is automatically recognized>, amount <currency also auto recognized> of money how much is 1 point profit & loss worth, possibility to open stop pending orders with either minimum required distance (or increase distance) where I clearly define for how many points EXTRA (so minimum plus what I define) must be stop pending orders placed away from current market price. Besides this, the information, that is the same for all currency pairs that I want to place pending orders for, is (by ''is'' i am referring to ''information''): magic number, lot size, trailing (in unit points), slippage (in unit points), take profit (currency auto recognized from logged in trading account balance), target loss (currency auto recognized). Those two take profit and target loss I define in amount of money as I previously said. I enable/tick the checkboxes near currency pairs that I want to schedule placements of stop pending positions. Extremely important for you to be aware of is that every single time when stop pending placements (by ''placement'' i mean opening of stop pending position) happens for strictly only checkbox ticked/enabled currency pairs, TWO (2 !!!!) stop pending orders are placed. One stop buy and one stop sell. ALWAYS TWO! Always those one that I said: one stop buy and one stop sell. Strictly only those two per one ticked/enabled (checkbox) currency pair. Then in the tool I have the option whether I want to make placements immediately upon clicking and confirming Open Trades button or on exact date+time (no limit how near or how far in the future) where timezone is predefined. Obviously tool must run at that time in order for operate. So at requested time stop buy and stop sell pending order(s) get placed. The main point of the tool and the most important thing is the following and due to extreme importance, I will type it in capitalized letters: WHEN ONE STOP PENDING ORDER GETS EXECUTED, THE OPPOSITE ONE MUST GET ALWAYS IMMEDIATELY (HERE WE MAY TALK ABOUT MILISECONDS OR EVEN NANOSECONDS - DEPENDING ON INTERNET CONNECTION) AUTOMATICALLY CLOSED WHILE BEING PENDING SO IT GUARANTEED NEVER GETS EXECUTED BUT AUTO-CLOSED INSTEAD. Example: if stop buy gets executed, stop sell of the same identical currency pair is automatically and immediately closed (cancelled) or vice versa: if stop sell gets executed, stop buy of the same identical currency pair is automatically closed (cancelled). Identity of currency pairs are verified per trade opening (placements and usage of Open Trades button) event. Having said that, this means the following: Lets say I open immediately ABCDEF currency pair. Two trading positions will be opened (pending): one stop buy and one stop sell. Then a second(s) or some time later I schedule the opening of ABCDEF again, either to be immediately placed (opened) or on particular date and time. So what happens is that one stop buy order and one stop sell order gets placed. Assuming that one out of two stop orders on first opening event hasn't been executed yet (other one auto-cancelled), I obviously have four stop pending orders: two stop buy and two stop sell. One stop buy and one stop sell is related to first opening event, one stop buy and one stop sell related to the second opening event. When one order gets execute, the opposite one of strictly only THE SAME SINGLE opening event gets auto-closed. So in that situation I remain with two stop pending orders. In, fortunately, extremely rare cases, the opposite order which must get, as most important feature in my tool, auto-closed (cancelled) may not be possible to be closed due to whatever reason: mostly related to the broker (e.g. ''price is too close to the market price''). In case if it cannot be auto-closed then there is already implemented additional feature, which takes care for all the time closing reattempts until that stop pending order, which remains being pending, is successfully closed. Similar logic for prohibited closing for executed orders (based on TP, SL, Trailing): auto reattempt of closing is already implemented. Available currency pairs can be listed on one or on multiple pages: depending on how many of available trading assets have single currency on either left or right side of the symbol.

This was extremely brief description of entire tool. If you need longer, let me know. However, I need to say that I need your help when it comes to bug solving for strictly only one feature becaue everything else works good. Unfortunately, the problematic feature is the most important feature.

So finally I need your bug solving help with the following:

As I said, tool is placing two opposite stop pending orders, We need to ensure that as soon as one pending order is converted to market order (executed), the other order gets deleted. We need to ensure this for GUARANTEED 100% of the scenario. It must work for all brokers. It must work for all type of accounts. The pending orders could be placed for one symbol at a time or it may be placed for multiple symbols at a time. The distance between pending orders could be zero theoretically for the brokers who supports it. The main thing what I need from you as the problem solver is your understanding that it may happen that both stop buy and stop sell positions could get executed at identical time but still one, that could had been executed just a little bit later, we are talking almost about nanoseconds here, MUST 100% guaranteed ALWAYS be prevented to be executed and auto-closed instead. If cannot be auto-closed immediately then feature already works for all the time reattempts to be successfully closed.

The main bug is that EXTREMELY rarely it happens that both positions still get executed and I would really need 100% guaranteed solution that the one, that at least for very little time, remains being pending (NOT executed!) is for sure auto-closed (cancelled). I need this problem solved so remaining one will be for sure always auto-closed.

Kindly check demonstration on the following video that I uploaded - let me know if you would require any different file uploading website in order to be willing to download the file:

https://www.sendspace.com/file/sw5kuf

If you have any problems accessing link and/or downloading file, kindly let me know.

For you to imagine how rare the problem is and how much near the perfection this feature is already implemented, I would like to give you the following information: In order to catch this one single situation of a bug, I had to do testing of same single feature for over one week, in average 10 hours per day, most of opening events had multiple ticked/enabled (in checkboxes) currency pairs and tests were done in multiple terminals of different brokers. In total I believe I had over 1000 opening events, either set to Immediately (Right Away) or defined date+time (timezone in pre-settings window). This was one, very very hard to catch situation, where bug occurred. In each and every other opening event, the feature worked well: opposite stop order (the one that remains being pending at least for very little time) got successfully auto-closed, with or without reattempts. However, I would really need this to work 100% of times. Guaranteed 100%. This means if in next several decades, there will be 100000000 opening events, each containing lets say 4 ticked currency pairs, then 400000000 times should be opposite order successfully auto-closed (prevented to be opened). So I am wondering if anyone could please help me to reach 100% of success when it comes to auto closing.

From you I would need both text based description of your bug solution: what exactly did you do and giving to me, for this single piece of code, guaranteed to be related strictly only to problematic feature and not any other one, your fixed version of the code. However, I would also need that you provide me the full development code which includes your solved problematic features. So once again I repeat: I need from you separately giving to me once only the code with only this single feature (solved by you) and once ENTIRE tool which includes modified that single feature.

I will provide entire code if/when you bid and contact me. For any questions, you are very welcome to ask. Thank you very much in advance.