Replies: 4 comments 11 replies
-
Sounds like something is definitely wrong there. My first thought is system config. generate_force_roll_orders should only run once, not in a loop like most of the stack handler functions. (Although as I write that, I think that would only generate the instrument orders, not contract orders...still, I'd check that anyway because it's easy.) Second, run interactive order stack and paste the instrument and contract order stacks so we can see what you're looking at (picture == 1000 words, etc.) You'll probably then need to provide the output from the stack handler that caused this. |
Beta Was this translation helpful? Give feedback.
-
That is weird. Yes please paste in the logs. |
Beta Was this translation helpful? Give feedback.
-
Ok, so an order is being submitted, IB doesn't like it, and the algo runs out of time so gives up. Rinse and repeat. There are two issues here:
The first I can probably diagnose and fix quite easily. The second is trickier. The only thing that seems odd just off the top of my head is that it's a market order, but has a limit price. I won't have the time today, but you could try setting up the order as a minimum example just using ib insync and posting to https://groups.io/g/insync/topics |
Beta Was this translation helpful? Give feedback.
-
Hi Rob, By way of update, I noticed I was couple weeks behind in the latest source tree, synced to the latest yesterday. There have been some updates on exchange times and ib client classes. Long story short this morning, it rolled NIKKEI positions with no hassle. I wonder whether this had to do with timing, for some reason previously the stack handler thought that it should give market orders vs. best strategy due to timing, and somehow that didn't work well with force spread rolls. I see now it uses the "best" strategy. Thanks everyone for their time. |
Beta Was this translation helpful? Give feedback.
-
Hi Everyone,
I am trying to force roll 5 NIKKEI contracts from Dec to March. I have noticed that on instrument order stack I have a single spread order for 5 contracts, however when I look at contract or broker order stacks, I noticed that there are 20+ child orders.
Just wanted to check whether this is expected behavior, nothing has filled yet, but want to make sure the stack handler won't overtrade.
Best,
Emre
Beta Was this translation helpful? Give feedback.
All reactions