I am running standard Version: MultiCharts64 Version 14.0 Release (Build 25793) with Rithmic. If I'm trading on SIM I cannot cancel trades or close them in the DOM or the chart, and the DOM shows that I am flat even though I have trades open. The order and position tracker show the open trades but I cannot close them.
I shut down MC and restarted but that did not work. I want to get this resolved just in case this problem is present running realtime.
Any ideas
If I'm trading on SIM I cannot cancel or close trades. [SOLVED]
-
Kate MultiCharts
- Posts: 597
- Joined: 21 Oct 2020
- Has thanked: 9 times
- Been thanked: 148 times
Re: If I'm trading on SIM I cannot cancel or close trades.
Hello,
When the behaviour occurs, please send us a report so that we could investigate it.
Main MultiCharts window → Help → Feedback.
In the Feedback window select the following options:
When the behaviour occurs, please send us a report so that we could investigate it.
Main MultiCharts window → Help → Feedback.
In the Feedback window select the following options:
- Attach a screenshot; (make sure the issue is visible or attach additional screenshots here)
- Attach log files…;
- Snapshot of the current MC setup;
- Open workspaces…;
- Upload collected data to Help Desk;
- uncheck other options and click Send.
Re: If I'm trading on SIM I cannot cancel or close trades.
OK will do. Thanks.
OK I just started the MC platform and placed an order on SIM and the problem is still occurring. I sent the info as you requested and I also attached another screenshot to this window to further illustrate the issue.![Image]()
OK I just started the MC platform and placed an order on SIM and the problem is still occurring. I sent the info as you requested and I also attached another screenshot to this window to further illustrate the issue.
- Attachments
-
- Example.jpg
- (293.34 KiB) Not downloaded yet
Re: If I'm trading on SIM I cannot cancel or close trades. [SOLVED]
Hi Kate. I did a fresh install and that seemed to do the trick. I tried to repair it and use the backup but apparently the bug was a little deeper in the platform than the backup and repair could resolve so it was apparently just a corrupt file somewhere. Thanks for your help!