ArbicsxPedia
···

Synchronization problems

How to resolve misalignments between broker and dashboard

Updated 16/07/2026 · 2 min read

"Synchronization problems" are the category of anomalies where the data shown in the dashboard does not coincide, for a certain time interval, with what you see on the broker. In the vast majority of cases, the cause is technical and temporary.

How they manifest

Typical signs:

  • open trades present on the broker but not yet visible in the dashboard (or vice versa);
  • overage netto updating with a delay;
  • performance metrics not aligned with the actual period;
  • funded cycle status stuck compared to what you expect.

In the vast majority of cases, by waiting a few minutes, the data will realign automatically.

Frequent causes

  • unstable network on the user side;
  • update in progress on the broker side;
  • platform maintenance moment;
  • connection parameters no longer valid (for example, expired on the broker side).

Do not reconnect the broker multiple times in a row. If a synchronization cycle is in progress, close attempts can confuse it.

Recommended checks

  1. Wait a few minutes and refresh the dashboard.
  2. Verify your connection and close any background processes.
  3. Check the account and order status on the broker.
  4. Consult the category Updates, releases, and maintenance for official communications.
  5. If necessary, perform a new connection of the broker following the guide How to connect the broker.

What not to do

  • Do not draw operational conclusions from temporarily misaligned data.
  • Do not modify sensitive configurations in an attempt to "fix" the synchronization.
  • Do not publish screenshots with partial data as if they were definitive.

Arbicsx provides technological software pursuant to D.Lgs. 58/1998 (TUF): the metrics are descriptive of the observed state. During a misalignment, some metrics might reflect a transient moment that is not representative.

Synchronization and perception

Those who use the dashboard daily develop over time a sensitivity to normal synchronization times. When they deviate, they notice immediately. Those who are at the beginning tend instead to interpret as a "problem" what is normal reading flow. A useful little exercise is to mentally note the typical times in the first few days: it will become your future reference base.

Remember also that perfect synchronization in real time is not realistic: there is always a minimum technical gap. The quality of a platform does not lie in completely eliminating this gap, but in making it predictable and non-impactful on the operational experience.

Mental references

  • Typical times observed in the first few days.
  • Platform behavior in normal moments.
  • Distinction between natural gap and anomalous misalignment.

If synchronization is not restored

If after reasonable times the data does not realign, open a ticket from the support with:

  • start time of the misalignment;
  • metrics or data involved;
  • any observed difference compared to the broker;
  • checks already carried out.

The support team verifies if the misalignment is isolated or part of a broader case. For problems that seem accompanied by a real disconnection, first consult What to do in case of disconnection.

Feedback

Was this guide helpful?

Need help?

If this guide wasn't enough, our team is available.

Every request is routed to the correct channel. Contact us and receive a structured reply as quickly as possible.

Go to support