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

Timestamp for this request is outside of the recvWindow. #43

Closed
4 tasks done
AlexCatarino opened this issue Jan 22, 2025 · 2 comments · Fixed by #44
Closed
4 tasks done

Timestamp for this request is outside of the recvWindow. #43

AlexCatarino opened this issue Jan 22, 2025 · 2 comments · Fixed by #44
Labels
bug Something isn't working enhancement New feature or request

Comments

@AlexCatarino
Copy link
Member

Expected Behavior

Orders are not invalid due to recvWindow.

Actual Behavior

Brokerage Warning: Order failed, Order Id: 18 timestamp: 1/20/2025 3:59:59 PM quantity: -0.013 content: {"code":-5028,"msg":"Timestamp for this request is outside of the ME recvWindow."}

Potential Solution

Set the recvWindow up to 5000, since Binance doesn't recommend higher. Example:
https://developers.binance.com/docs/derivatives/option/general-info#example-1-as-a-query-string

Checklist

  • I have completely filled out this template
  • I have confirmed that this issue exists on the current master branch
  • I have confirmed that this is not a duplicate issue by searching issues
  • I have provided detailed steps to reproduce the issue
@AlexCatarino AlexCatarino added bug Something isn't working enhancement New feature or request labels Jan 22, 2025
@AlexCatarino
Copy link
Member Author

The msg (in this case, "Timestamp for this request is outside of the ME recvWindow.") should be saved as an order ticket tag, the orders simply receive "Binance Order Event"

@Martin-Molinero
Copy link
Member

Martin-Molinero commented Jan 29, 2025

  • improve error message
Image
  • When placing an order, ExecuteRestRequest has a rate limit, which will make the timestamp potentially be off, we could get passed the rate limit before

  • Kind of related to Implement Rate Limit per Rest Client #22 too

@Romazes Romazes mentioned this issue Jan 29, 2025
16 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants