Problem or use case
I am using scalable-cli for algorithmic tranche trading (grid bot). I intentionally need to place multiple identical limit orders (same ISIN, same side, same limit, same quantity) in rapid succession.
Currently, the CLI blocks identical orders placed shortly after one another. To get around this, I have to artificially modify the limit price by 0.01 € or the quantity by 1 share for each tranche, which messes up the strict grid logic.
Proposed solution
Introduce a --force-duplicate flag to explicitly opt-in and bypass this protection.
Questions for Maintainers
Before I open a PR, I'd like to understand the backend behavior:
Is this duplicate protection purely client-side in the CLI, or does the Scalable Backend API (Idempotency Key / Replay Protection) block identical payloads in the same time window anyway?
If it's a backend constraint (time-based cooldown), what is the exact timeframe before an identical order is accepted again?
If the API allows it, would you accept a PR for a --force-duplicate flag to bypass the client-side check?
Alternatives considered
Varying the limit price by 1 cent (e.g., 1.50 -> 1.51).
Varying the quantity by 1 share.
Both work but break the strict logic of the trading algorithm
Relevant command or workflow
sc broker trade buy --isin --shares --limit --force-duplicate
User impact
Important for a specific workflow
Checklist
Problem or use case
I am using scalable-cli for algorithmic tranche trading (grid bot). I intentionally need to place multiple identical limit orders (same ISIN, same side, same limit, same quantity) in rapid succession.
Currently, the CLI blocks identical orders placed shortly after one another. To get around this, I have to artificially modify the limit price by 0.01 € or the quantity by 1 share for each tranche, which messes up the strict grid logic.
Proposed solution
Introduce a --force-duplicate flag to explicitly opt-in and bypass this protection.
Questions for Maintainers
Before I open a PR, I'd like to understand the backend behavior:
Is this duplicate protection purely client-side in the CLI, or does the Scalable Backend API (Idempotency Key / Replay Protection) block identical payloads in the same time window anyway?
If it's a backend constraint (time-based cooldown), what is the exact timeframe before an identical order is accepted again?
If the API allows it, would you accept a PR for a --force-duplicate flag to bypass the client-side check?
Alternatives considered
Varying the limit price by 1 cent (e.g., 1.50 -> 1.51).
Varying the quantity by 1 share.
Both work but break the strict logic of the trading algorithm
Relevant command or workflow
sc broker trade buy --isin --shares --limit --force-duplicate
User impact
Important for a specific workflow
Checklist