ProtoOaOrderErrorEvent TRADING_BAD_STOPS returns neither OrderID nor positionID
ProtoOaOrderErrorEvent TRADING_BAD_STOPS returns neither OrderID nor positionID
06 Jun 2024, 14:03
2024-06-06 12:30:00.445275 0ms WARN ProtoOaOrderErrorEvent {
ctid_trader_account_id: 000redacted000,
error_code: "TRADING_BAD_STOPS",
order_id: Some(
0,
),
position_id: Some(
0,
),
description: Some(
"New TP for BUY position should be >= current BID price. current BID: 0.66466, TP: 0.66464",
),
}
@PanagiotisCharalampous could you pls advise on this one?
Replies
PanagiotisCharalampous
23 Jul 2024, 06:36
Hi Raul,
I have forwarded this issue to the product team. I will update the thread when I receive a response.
Best regards,
Panagiotis
@PanagiotisCharalampous
raul_gherman
13 Aug 2024, 16:01
seems demo environment has version 92 deployed:
2024-08-12 16:42:54.995733 0ms INFO tokio-runtime-worker [src/process_message_stream.rs:108] ProtoOaVersionRes {
payload_type: None,
version: "92",
}
still, TRADING_BAD_STOPS error returns the same:
2024-08-13 05:00:39.064768 0ms ERROR tokio-runtime-worker [src/process_message_stream.rs:187] ProtoOaOrderErrorEvent {
payload_type: None,
ctid_trader_account_id: 40xxxxx2,
error_code: "TRADING_BAD_STOPS",
order_id: Some(
0,
),
position_id: Some(
0,
),
description: Some(
"New TP for SELL position should be <= current ASK price. current ASK: 0.52324, TP: 0.52335",
),
}
@raul_gherman
raul_gherman
13 Aug 2024, 16:01
seems demo environment has version 92 deployed:
2024-08-12 16:42:54.995733 0ms INFO tokio-runtime-worker [src/process_message_stream.rs:108] ProtoOaVersionRes {
payload_type: None,
version: "92",
}
still, TRADING_BAD_STOPS error returns the same:
2024-08-13 05:00:39.064768 0ms ERROR tokio-runtime-worker [src/process_message_stream.rs:187] ProtoOaOrderErrorEvent {
payload_type: None,
ctid_trader_account_id: 40xxxxx2,
error_code: "TRADING_BAD_STOPS",
order_id: Some(
0,
),
position_id: Some(
0,
),
description: Some(
"New TP for SELL position should be <= current ASK price. current ASK: 0.52324, TP: 0.52335",
),
}
@raul_gherman
PanagiotisCharalampous
19 Aug 2024, 05:14
Hi Raul,
The team confirmed this is a bug and it will be solved in an upcoming update.
Best regards,
Panagiotis
@PanagiotisCharalampous
raul_gherman
22 Jul 2024, 11:48
@spotware support, could you please take a look at this topic?
topic raised 1.5 months ago, in the mean time v9.1 was released, issue still relevant.
could you please take a look, or at least reply here that it is going to be addressed or not?
@raul_gherman