-
Notifications
You must be signed in to change notification settings - Fork 2
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
Open position failed: Pulling Option info faild #5
Comments
Expired options are not supported,please confirm whether the option has expired.
If the problem still exists, Provide log information as follows.
https://openapi.moomoo.com/moomoo-api-doc/en/qa/opend.html#7649
发件人: ***@***.*** ***@***.***> 代表 quasifin
发送时间: 2024年5月26日 2:31
收件人: MoomooOpen/py-moomoo-api ***@***.***>
抄送: Subscribed ***@***.***>
主题: [MoomooOpen/py-moomoo-api] Open position failed: Pulling Option info faild (Issue #5)
We're trying to do market BUY orders using OpenD and this SDK. It was working great for months then we started getting this error coming from the OpenD server: "Open position failed: Pulling Option info faild" (faild is not a typo, we are receiving it this way).
As an example, we tried to BUY a QTY of "2" of "US.SPY240521P522000" as a "MARKET" order.
Those errors started to appear on all orders starting May 17th 2024.
We cannot find any reference to this error in the documentation and MooMoo support told us that the error is not coming from OpenD even tough we thoroughly confirmed that it was in fact coming from the OpenD server.
Using OpenD Ver.8.1.4108 with SDK Ver.8.1.4108
—
Reply to this email directly, view it on GitHub <#5> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBDO3CQ626MAZSGH7LOSGHDZEDKFXAVCNFSM6AAAAABIJC4H3WVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMYTOMJWHA3DCMA> .
You are receiving this because you are subscribed to this thread. <https://github.com/notifications/beacon/BBDO3CS7JCO4TRSTGBFJTLDZEDKFXA5CNFSM6AAAAABIJC4H3WWGG33NNVSW45C7OR4XAZNFJFZXG5LFVJRW63LNMVXHIX3JMTHIUHJP4I.gif> Message ID: ***@***.*** ***@***.***> >
|
Hi, can you provide your moomoo ID, so that we can check what is the exact problem. You can also try to restart your OpenD, and see if the problem is still there.
From: ***@***.*** ***@***.***> On Behalf Of quasifin
Sent: Sunday, May 26, 2024 2:31 AM
To: MoomooOpen/py-moomoo-api ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [MoomooOpen/py-moomoo-api] Open position failed: Pulling Option info faild (Issue #5)
We're trying to do market BUY orders using OpenD and this SDK. It was working great for months then we started getting this error coming from the OpenD server: "Open position failed: Pulling Option info faild" (faild is not a typo, we are receiving it this way).
As an example, we tried to BUY a QTY of "2" of "US.SPY240521P522000" as a "MARKET" order.
Those errors started to appear on all orders starting May 17th 2024.
We cannot find any reference to this error in the documentation and MooMoo support told us that the error is not coming from OpenD even tough we thoroughly confirmed that it was in fact coming from the OpenD server.
Using OpenD Ver.8.1.4108 with SDK Ver.8.1.4108
—
Reply to this email directly, view it on GitHub <#5> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBDO3CQ626MAZSGH7LOSGHDZEDKFXAVCNFSM6AAAAABIJC4H3WVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMYTOMJWHA3DCMA> .
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're trying to do market BUY orders using OpenD and this SDK. It was working great for months then we started getting this error coming from the OpenD server: "Open position failed: Pulling Option info faild" (faild is not a typo, we are receiving it this way).
As an example, we tried to BUY a QTY of "2" of "US.SPY240521P522000" as a "MARKET" order.
Those errors started to appear on all orders starting May 17th 2024.
We cannot find any reference to this error in the documentation and MooMoo support told us that the error is not coming from OpenD even tough we thoroughly confirmed that it was in fact coming from the OpenD server.
Using OpenD Ver.8.1.4108 with SDK Ver.8.1.4108
The text was updated successfully, but these errors were encountered: