New Hope Feed Restored: Reconnection Checks and Archive

Updated October 14, 2026. The original publication dated October 12, 2021 announced the completion of work on New Hope Feeds. It followed the September 30, 2021 incident notice. This page retains that historical purpose; it does not establish the current availability of a particular connection.

The connection is back: can the bot restart immediately?

Check the data and account state first. An open connection does not establish how fresh the first price is, whether every subscription has recovered or whether order records agree. Market-data recovery and trading-channel recovery are separate checks because they can complete at different times.

The old notice listed feeds and package arrangements from 2021. Those names are not presented here as a current specification or a promise of an included service. For the current NH PRO configuration, consult its current manual and the scope of the selected package.

First, establish that the data is fresh

For every required instrument, record the latest update time, current bid/ask and trading-session state. Check a sequence of new messages, rather than one successfully displayed tick. If the application records both source time and receipt time, do not mix them in a latency calculation.

For example, a window reconnects at 10:10 while the latest stored quote is timestamped 10:00. That may be a valid historical record, but it must not automatically be treated as the current price. This is a hypothetical example. Our fast-feed evaluation guide explains how to compare times and prices.

Second, reconcile orders and positions

Before resuming automated actions, obtain the broker's current open positions and working orders. Reconcile them with the application's local records. If an order was submitted before the disconnect, a missing response does not prove rejection: establish its status using its identifier first.

Resending an order “just in case” can create an additional order. Similarly, a repeated execution report after reconnection should not be counted as a new fill without checking its identifier. These are state-verification requirements; they do not assert that every New Hope version automatically implements a particular recovery algorithm.

A short post-interruption acceptance checklist

1. The intended application version, account and trading environment are selected.

2. The required instruments are subscribed and fresh quotes keep arriving.

3. The computer clock and time zone have been checked.

4. Open positions and remaining order quantities agree with broker records.

5. Unacknowledged actions have been resolved and duplicates ruled out.

6. Logs are retained and the stopping procedure for another error is known.

Write the expected outcome before running the check. For example, after reconnection the account should still have one 0.10-lot position, rather than two. That criterion is more informative than “the connection indicator turned green”. Continue the submission, fill and cost checks with our execution-audit method.

Document the recovery

Keep the observation start time, component versions, instruments and outcome of each check. In the MetaTrader 5 environment, the virtual-hosting documentation describes separate terminal and Expert Advisor journals. Use the corresponding application and connection logs in another environment.

If data or positions disagree, resolve the discrepancy first. A verified connection is necessary for operation, but does not guarantee profit. In a message to New Hope, provide the version, event time, source and reconciliation results without passwords or secret keys. This supports a concrete investigation instead of relying on an old service-status notice.