RTX5 Help and Troubleshooting

Open Download and choose the published Windows package approved for your operating system and architecture. Match the build to its release record.

Check the supplied SHA-256 digest and the installer’s publisher signature. Ask RTX5 for missing verification details before proceeding.

Use the broker’s documented installation steps, then connect to the supplied server. Confirm whether the selected account is demo or live before placing an order.

Confirm the exact server address, account identifier and intended account role with the broker. Use its official login or recovery workflow.

If authentication fails, check the server selection, account status and client/server compatibility before retrying. Read-only access may have different permissions from trading access.

Use the broker’s password-reset or account-recovery process if credentials are rejected. Share the error and client build with support without sending passwords or verification codes.

Obtain the broker’s approved endpoint, account type and compatible client version. Confirm network access and avoid guessed server addresses.

After sign-in, check account identity, market-data timestamps and open orders. A connected icon alone does not prove every data feed is current.

After a disconnect, restore the session and compare active orders and history with your last known state. Establish the result of pending commands before resubmitting them.

Select an instrument available to the account, check the timestamp of its latest data and choose a supported timeframe and chart type.

Add only indicators supported by the build. Review required data, parameters and dependencies; a calculation or chart overlay does not by itself authorize order submission.

Save or export a workspace only through a documented function in your build. If a chart freezes, compare another instrument and report the data timestamp, build and reproduction steps before changing saved settings.

Confirm the account, instrument, current quote, trading hours and permitted volume. Review whether the requested order and protection types are supported.

Submit the instruction and retain the server acknowledgement or rejection. An accepted order is different from a completed fill; inspect resulting status and executed quantity.

For modifications or closures, inspect the current server-held state first. After an interruption, check active orders and history before repeating a command. Ask the broker to investigate ambiguous outcomes.

Confirm the supported alert condition, delivery channel and account permission. Check device notification permissions where the released client uses them.

Test a harmless condition in a demo environment. Compare the alert event time with delivery time and confirm which account and instrument it references.

If delivery fails, review the connection and device settings and record the condition, build and timestamp. An alert is a notification; it does not guarantee an order or a price.

Check the algorithm’s source rights, supported SDK/runtime version and dependencies. Distinguish an indicator that displays data from a bot allowed to submit orders.

Test using the desktop workflow and declared data/cost assumptions. Review data access, trading permissions, quotas and broker eligibility before requesting hosted execution.

For a start or stop request, inspect the server acknowledgement, instance status and logs. Confirm whether stopping also changes existing positions; do not assume phone disconnection stops a hosted process.

Confirm the broker’s supported payment route, identity requirements, fees and reference format. Distinguish a platform-licence invoice from a trading-account transaction.

Keep the transaction reference and inspect the broker’s pending, approved, rejected or settled status. An on-screen request does not establish receipt of funds.

For missing or duplicate amounts, compare the provider reference with the cash and credit ledger. Request reconciliation or refund handling from the responsible broker/provider.

Use the official store link only once it is published and approved for your region/device. Confirm the client and broker-supported build before sign-in.

After an interruption, authenticate and refresh the account’s positions, orders and history. Reconcile any command sent before connection was lost.

For a hosted bot, check the broker runtime’s status independently of the phone. Backtesting belongs to the proposed desktop workflow.

Identify the signed-in staff role and its tenant, group and account scope. Ask an authorized administrator to confirm the permission policy for the requested action.

If a withdrawal, pricing or routing change requires approval, follow the configured review workflow. A denied action is not a reason to use another person’s credentials.

Record the action, time, target scope and audit/reference identifier. Request a policy review and repeat the permitted workflow after an authorized change.

Record the client/build, OS or browser, broker endpoint, affected task and exact time. Describe expected behavior and the observed result.

Check whether the problem affects login, market data, orders or a particular algorithm. Preserve references needed for reconciliation and avoid repeated ambiguous order submissions.

Send reproduction steps and sanitized diagnostics to the support channel. Never include passwords, access tokens or payment credentials.

Decide whether the task needs a trading/account API, a counterparty FIX session or the RX5 development toolchain. Confirm authentication, role and environment.

Use the relevant documentation to define request/response or session scope. Confirm idempotency, rate limits, recovery and version compatibility before integration.

Validate sanitized examples in the agreed sandbox and record the build and outcome. A protocol name or researched provider does not establish live integration access.

Start with the account and connection indicators. Confirm the broker endpoint, demo/live status and account permissions before using any trading controls.

Find the instrument list, chart area and order entry controls using the client’s supported navigation. Check the instrument and current quote when switching between panels.

Locate active orders, positions and completed history. Use these server-backed records to distinguish a submitted instruction from an executed trade; save a layout only if that function is documented for your build.