Support Board
Date/Time: Wed, 22 Apr 2026 02:50:36 +0000
Post From: Trade/Quote Symbol unexpectedly changed without warning, triggering Daily Loss Limit
| [2026-04-22 01:06:06] |
| soranthous - Posts: 6 |
|
I have replicated the issue and it most definitely occurred when copying one drawing from a chart to another. I am attaching 2 chartbooks. I have removed all studies etc. as per the instructions for attaching chartbooks. The file named "MNQ(continuous) - Copy" is a copy (with all studies removed) of a chartbook last modified on April 13th. That was the last time I opened Sierra chart, prior to today (April 21). I was able to replicate the issue because the only things I did this morning to change anything on the chartbook (aside from the automatic chart updates due to new trading data) was to add chart drawings, and specifically, copy a particular drawing from one specific chart to another. Note how in the chartbook named "Symbol Issue" there is a chart drawing (a horizontal ray) on chart #24 at price 26885.25. I wanted this horizontal ray to be copied over to chart #17, so under chart settings-->chart drawings, I had added 24 to the field "Copy Chart Drawings From Chart #'s" I then replicated this exact procedure on the file named "Copy", which did not have the chart drawing in question (as it is a copy of my chartbook last modified on April 13th-just altered to remove all studies). Lo and behold, the symbol on my DOM surreptitiously changed from NQM6/MNQM6 to just NQ. My chartbook has had the setting for linking the symbol enabled for months with no issue. There is some interaction between adding an additional chart to the "Copy Chart Drawings From Chart #" field, and the toggles for Chart Settings-->Linking->Symbol, and possibly Trade Window and/or Trade/Quote Symbol. In the attached Chartbook named "Copy", please try placing a chart drawing in chart #24, then going to chart #17 and within the field "Copy Chart Drawings From Chart #", add 24 to that list. Please confirm whether or not the Symbol on the DOM changes as a result of this action, because that is what happened to me and it is how I replicated the issue. |
Private File Private File |