Support Board
Date/Time: Thu, 20 Feb 2025 19:51:14 +0000
Account Numbers Reset Upon Data Connection Loss/Restore
View Count: 641
| [2021-01-11 00:53:28] |
| User279754 - Posts: 38 |
|
I trade multiple automated systems for a given market (e.g. multiple unique systems for the NQ, ES, YM markets). As such, I have to use a unique sub-account number with my broker for each system so that trade signals don't interfere with each other. I am using Denali and Sierra order routing data services and I'm experiencing a disruptive issue where all of the accounts associated with my respective systems get reset to one default account whenever data connection is lost and then restored. I should also note that I have a main instance of Sierra Chart and a sub-instance running as well, and the issue only appears to affect the sub-instance (I use the DTC-Sub Instance service configuration). This resetting of the account numbers poses substantial risk, as it can cause trade signals to conflict and/or be ignored. Is there a setting within Sierra Chart that addresses this so that the account numbers stay static once I set them up? If not, do you have any suggestions for mitigating this issue? Thank you in advance for your thought and assistance. Date Time Of Last Edit: 2021-01-11 00:57:51
|
| [2021-01-11 00:57:32] |
| |
|
and I'm experiencing a disruptive issue where all of the accounts associated with my respective systems get reset to one default account whenever data connection is lost and then restored. We will address this in the next release.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2021-01-13 04:45:21] |
| User279754 - Posts: 38 |
|
Thank you for the swift response. I just wanted to point out that I edited my original message after you had already responded, so you may have missed a detail that may be relevant--I have a main instance of Sierra Chart and a sub-instance running as well, and the issue only appears to affect the sub-instance (I use the DTC-Sub Instance service configuration). Hopefully that's helpful in terms of any enhancements that need to be implemented for the next release. Thank you. |
| [2021-01-13 06:40:57] |
| |
|
The next release is out. 2219. This issue should be resolved.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2021-01-13 06:41:05
|
| [2021-01-17 06:13:47] |
| User279754 - Posts: 38 |
|
It appears 2219 and 2220 are Pre-Release versions currently--are these safe to use? Also, did the Denali symbol conventions change between 2207 and 2220? It appears NQH21-CME is now NQH21_FUT_CME, as one example...is that correct?
|
| [2021-01-17 22:50:53] |
| User279754 - Posts: 38 |
|
So I upgraded to v2220 and found that the same issue occurred this afternoon after my Sierra Chart sub-instance lost its connection. The odd thing is that some of my chartbooks maintain their account associations and some default back to my main account. Also, my main instance of Sierra Chart running on the same server did not lose any of its account associations.
|
| [2021-01-18 09:43:04] |
| |
|
Refer to: Software Download: About Prereleases. Are they Stable? It appears NQH21-CME is now NQH21_FUT_CME, as one example...is that correct? No this is not true. symbols like this are for the SC order routing service:NQH21_FUT_CME Use this Edit menu command to Translate the symbols to the current service: Edit Menu: Edit >> Translate Symbols To Current Service So I upgraded to v2220 and found that the same issue occurred this afternoon after my Sierra Chart sub-instance lost its connection We have looked into this and determined the problem. We will have a new version out that resolves this.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: