INSIDE 2.4: Release Archive and Log Validation

Updated October 14, 2026. The original June 1, 2020 announcement described INSIDE 2.4 for several connection variants. This page preserves the release context and adds a method for checking similar updates. Features of an old release should not automatically be attributed to current NH PRO.

What the 2.4 announcement listed

The notice described updates to MT4/MT5 communication protocols, data exchange between Feed and INSIDE, trailing-stop formulas and instructions. Variant-specific items covered MT4/MT5 logs, spread settings and slippage displays for 2Leg, and profit and slippage information in FIX API logs.

Improved tick handling during high volatility was a release claim, not an independently measured result presented in the article. The original publication did not include a test dataset from which today's performance could be calculated. The useful next step is therefore to validate a specific change in a defined configuration.

Separate three types of change

• Connectivity: the application receives data and server responses.

• Trading behaviour: order and position-management parameters match the selected settings.

• Reporting: the interface and logs correctly display events that have already occurred.

Correcting a logged number does not necessarily change trade execution. An improved slippage display, for example, does not establish that the broker now provides better fills. First reconcile the order identifier, requested price, actual fills and calculation units. The trading-bot execution audit explains that sequence.

Keep comparable logs before and after

Record application and platform versions, test times and the time zone. Choose a small, reproducible scenario: connection, receipt of a quote, submission of a valid test order, response, and cancellation or execution. Change only the necessary component so that a different server or revised settings are not mistaken for the effect of the update.

MetaTrader 5 separates platform and Expert logs. Both may be useful in a diagnosis. Do not assume that MT5 folder names or log formats also apply to a standalone application or FIX connection; consult the relevant documentation.

Check position-management parameters separately

1. Verify distance units: price, points or another measure.

2. Check the activation condition and subsequent level changes.

3. Record instrument restrictions and the response to a server rejection.

4. Establish behaviour when the application or connection is unavailable.

The trailing-stop article explains the general difference between a trailing mechanism and a fixed level. It is an educational explanation, not evidence that every INSIDE release implements a particular algorithm.

For the present product, consult the NH PRO manual and configuration preparation guide. If you have an old installer or an ambiguous log, send the version, time and a redacted excerpt through the support form. Keep passwords and secret keys out of diagnostic material.