Guide for the forthcoming edition. The old version 3.14 PDFs are retained as an archive, not instructions for this edition. Replacement PDFs follow completed acceptance checks.
Renew without replacing program files
Import the next signed monthly license file. No central paid activation service or renewal code is required. Validity includes the complete first day of the following month in Dubai; the stored signed expiry is the reference.
Paid expiry blocks new entries, while management of previously owned positions remains independent of commercial expiry and must recover safely after restart. It still requires a connected broker and verified ownership; this is not a guarantee of uninterrupted software protection.
Do not repeat uncertain orders
If an operation is Unknown, pause new entries, inspect the broker account and preserve intake, execution and protection records. Reconcile the result before retrying. Never delete state or repost a signal to force an uncertain operation through.
After restart, verify the exact account and server, then resolve ownership or pending-action holds. Manual and foreign positions must not be adopted automatically. Broker-held stops remain subject to broker execution conditions.
Back up and request help
Preserve the application private directory and license files separately from program updates. Windows-protected credentials and Telegram sessions may need deliberate sign-in again after moving devices. A backup restore does not start trading or change a device license.
Central password recovery is unavailable for the new local account. Keep the password safely. Share only a redacted error, software version, time and license reference with support; never share passwords, API Hash, Telegram codes or session files.
Reports must be compared with the broker statement. The loopback address 127.0.0.1 is local to the computer; remote access requires a separate secured arrangement. Browser notifications are not guaranteed after the browser closes.