Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: stop order rejection reason is REJECTION_REASON_UNSPECIFIED #10975

Closed
bglownia opened this issue Mar 22, 2024 · 0 comments · Fixed by #10978
Closed

[Bug]: stop order rejection reason is REJECTION_REASON_UNSPECIFIED #10975

bglownia opened this issue Mar 22, 2024 · 0 comments · Fixed by #10978
Assignees

Comments

@bglownia
Copy link
Member

Problem encountered

Stop order API returns REJECTION_REASON_UNSPECIFIED. This is not unexpected value which is not present in StopOrderRejectionReason enum.

It looks like this is only value that is returned, even if there is obvious different reason.

image

Observed behaviour

Stop order API returns rejection reason not present in StopOrderRejectionReason enum

Expected behaviour

Proper rejection reason should be returned

Steps to reproduce

Submit stop order that will be rejected (ie on market where there is no position, or reach max stop orders per party).
Query GraphQL to check rejectionReason

Software version

v0.76.0-preview.1

Failing test

No response

Jenkins run

No response

Configuration used

No response

Relevant log output

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants