Not sure what's going on here, but here is my set-up. I have a couple strategies trading simultaneously and the limit/stoploss works fine during the day and many times overnight. However I've noticed today that I got a "FinalOrder" status at the end of the day, and found that all my orders were cancelled in ToS.
Here are some images of my preferences and one of the trades.
Preferences screen:

Order Manager:

ToS Order History:
Here are some images of my preferences and one of the trades.
Preferences screen:
Order Manager:
ToS Order History:
Rename
After waiting a bit, it turns out the limits were placed but the stop losses were rejected. Is this an issue with ToS?
It’s hard to say without having the strategy to analyze. But it’s normal for the FinalOrder to pause for a while before getting submitted to the broker. We designed it that way because some brokers won’t accept orders submitted too shortly after the market close.
That doesn't seem to be the issue. In the Order Manager the order is scheduled to be placed but Schwab returns an error. It doesn't seem to be a strategy or a WL issue but something with Schwab.
Occasionally an order gets an error during the day (this is an hourly strategy) but Schwab retains the existing order. At EOD, however, it randomly cancels either the limit or the stop order.
Occasionally an order gets an error during the day (this is an hourly strategy) but Schwab retains the existing order. At EOD, however, it randomly cancels either the limit or the stop order.
If any, what's the error message? Double click the order or look in the Log Viewer.
Here's the message log from this morning:
Message Log - Use the green Connect button to connect to a Broker. You may need to Configure it first.
Schwab Broker: Error Getting Orders: Generic error
Schwab Broker: 03:30:19 Exception Getting Orders: One or more errors occurred. (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (api.schwabapi.com:443))
03:30:47 Internet restored! Reconnecting...
Schwab Broker: Exception Checking Order Response: Object reference not set to an instance of an object.
Schwab Broker: Exception Checking Order Response: Object reference not set to an instance of an object.
Schwab Broker: Exception Checking Order Response: Object reference not set to an instance of an object.
Here are a couple examples of orders that were placed and were rejected or were placed on one side but not the other.

Message Log - Use the green Connect button to connect to a Broker. You may need to Configure it first.
Schwab Broker: Error Getting Orders: Generic error
Schwab Broker: 03:30:19 Exception Getting Orders: One or more errors occurred. (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (api.schwabapi.com:443))
03:30:47 Internet restored! Reconnecting...
Schwab Broker: Exception Checking Order Response: Object reference not set to an instance of an object.
Schwab Broker: Exception Checking Order Response: Object reference not set to an instance of an object.
Schwab Broker: Exception Checking Order Response: Object reference not set to an instance of an object.
Here are a couple examples of orders that were placed and were rejected or were placed on one side but not the other.
We can fix that Object reference error, but it won't change the result.
I'll experiment with Cancel/Replace GTC orders to see what can be found.
I'll experiment with Cancel/Replace GTC orders to see what can be found.
Thanks.
Separate note, but Schwab does not like Short orders being placed at GTC, at least for thinly traded ETFs. I get a rejection notice on those. It will accept an Day order, but not GTC.
Separate note, but Schwab does not like Short orders being placed at GTC, at least for thinly traded ETFs. I get a rejection notice on those. It will accept an Day order, but not GTC.
Canceling the GTC happens all throughout the days. Before placing the new orders the first thing that happens is canceling the order orders. It's just that during the trading day the new orders become Active quickly.
The last bar of the day is different like Glitch explained. The "Final Orders" aren't placed for another 15 minutes - and here's where the REJECT happens. It seems that in this case they're not being placed as OCO. After one order is placed, the other is rejected for a possible oversell condition.
We'll work on it.
The last bar of the day is different like Glitch explained. The "Final Orders" aren't placed for another 15 minutes - and here's where the REJECT happens. It seems that in this case they're not being placed as OCO. After one order is placed, the other is rejected for a possible oversell condition.
We'll work on it.
Thanks, let me know if you need any more data/info.
Your Response
Post
Edit Post
Login is required