Repository navigation
Log QRS reject status/error on account-facts sync_rejected - #397
Merged
Merged
Conversation
Publish currently collapses every non-200 QRS response into sync_rejected. Print status= and a bounded alphanumeric error= token so the next invoke shows the exact console reject reason without dumping secrets or bodies.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Publish collapses every non-200 QRS response into
sync_rejected. Logstatus=and a bounded alphanumericerror=token so the next/account-facts-syncinvoke surfaces the exact Workers reject reason (e.g.account_facts_identity_mismatch) without dumping secrets or bodies.Likely cause under investigation: sole-account fallback posts real
broker_account_idwhile QRS Firstrade binding may still bindaccount_selector/broker_account_idfrom the platform label.No trading-mode / strategy change.