How to open only 1 order when 2 graphs give the same signal

Hello I run the same EA on multiple graphics, it executes and order when the conditions are met at the open of a new candle. But sometimes more than one pair gives the signal at the same time resulting in two open order at exactly the same time, as shown in the picture.
Is there anyway to remedy this and prevent one of the orders from happening?

Both EA's run in different threads and are executed asynchronously. If they open positions at exactly the same time you need to force them into synchronous execution by using a mutex.

1. Create a mutex.
2. When the open signal is met let each EA aquire the mutex.
3. Once the mutex is aquired check if an open order already exists. If yes, don't open another one.
4. As only one EA can aquire the mutex at any given time, the EA trying to aquire it will have to wait for the EA that owns it.
5. This way the EA's don't work in parallel anymore, a precondition to achieve what you want.

A working implementation is here (it does a lot more things then you need), an actual use case here, lines 1049-1051 are never executed by more than exactly one EA (synchronous instead of otherwise asynchronous behaviour). GlobalVariableSetOnCondition() is your friend and starting point for investigation.

Ok thank you. So a mutex from my research is an external mqh file right?

It may be any "resource" accessible by a programing language with a defined way of managing access. In very simple terms it's a counter counting number of accesses of a resource. Such a resource may also be called a semaphore, and a mutex is a special semaphore: one with "mutual exclusive" access. It means it's a counter with the maximum number of simultanuous accesses of "1". If one code block aquires the resource, no other code block can (mutual exclusive). All others have to wait until the code which "owns" the resource releases it. Call it a "lock" if you want. In MQL you may use a window handle, a file handle, a special variable, or in the case of my framework it's just a regular MQL string stored in the chart.

GlobalVariableSetOnCondition() let's you create a locking mechanism using a global variable as the "resource" you can manage access for. Search for "GlobalVariableSetOnCondition" and "lock" at the MQL5 forum, there are some more example implementations. GlobalVariableSetOnCondition() is part of MQL especially for that purpose, for nothing else.

From the old MQL4 documentation:
The function provides atomic access to a global variable, so it can be used to provide a semaphore for interaction of several experts working simultaneously within one client terminal.