Tried the help@collective2.com account without much success, so I’m giving it a shot here:
At the end of the API explanation of the delay command, the instructions say that the emails to subscribers will be sent at the earlier of the following: 1) when your earliest delay time expires or 2) the first time you specify a trading signal with no delay.
Just to clarify a couple of points:
If a delay is attached to a signal, the signal is executed by C2 when the email is sent to subscribers (i.e. at the expiration of the delay), or immediately upon signal entry (i.e. only the email is delayed, not the
signal)?
In the following example, I’m long 1 lot of EUR/USD.
If I enter a signal to “close all open positions” with a delay of 60 seconds, and then immediately enter a signal to short 1 lot of EUR/USD, what is the order of execution? Is the delayed order executed first (that is, I close my open long on EUR/USD and then get short 1 EUR/USD), or is the non-delayed order entered first (that is, my short signal effectively flattens my position in EUR/USD, and then my “close all open positions” signal is ignored, so I end up with no position)?
Thanks.
Hi, INTJ,
I’m embarrassed to tell you that the option of delaying signal emails is no longer supported. (The “embarrassing” part is that the documentation still blithely goes on and on about the feature, which was removed some time ago. Sorry!)
So, nowadays, since we do not support the delaying of signal emails, then any delay times you specify will be ignored. Signal emails will be sent as quickly and efficiently as possible. (There is some minimal batching done to make the emailing more efficient, i.e. during a flurry of signal-posting activity, we may wait a few seconds to capture more signals before sending out an email, but overall you should assume signal emails are sent as soon as they are posted.)
The paragraph above concerns only the attempt to delay signal emails going out to subscribers. While this feature is no longer supported, we do still support delaying the processing of signals – which is what we call “parking” an order. You can specify that an order will be parked through the use of the parkuntil or parkuntildatetime parameters, as described in the API docs ( http://www.collective2.com/content/automation.htm ).
You final question asks about the sequence in which delayed orders are processed. However, I can’t really answer the question in any meaningful way, since: 1) the delays you asked about were actually email delays, not signal-processing delays; and 2) email delays are not supported any more, in any case.
I hope this answers your question adequately. If not, let me know.
Matthew
Thank you.
