The resolved bugs log collects the most significant corrections released over time in a single place. It serves you to understand if an issue you observed has been closed, and it serves the team to maintain a transparent memory of the work performed.
What we consider a bug
A bug is a software behavior that differs from the expected or declared one. It is not the same as a missing feature or a personal preference: the log deals with the former. New feature requests and behavior changes follow different paths.
What you find in each entry
- concise description of the problem, in non-technical language;
- expected impact, meaning who was involved and under what conditions;
- applied correction and the version in which it was released;
- possible instructions for users who had experienced the problem.
How they are identified
A bug reaches processing through multiple channels: user reports via ticket, internal error monitoring, pre-release checks. Well-structured user reports (with timestamps, screenshots, and steps to reproduce) are often decisive: the guide How to submit an effective request explains how to do it well.
Correction priority
Not all bugs are equal. A problem that completely blocks a critical function for many users is addressed before a visual annoyance affecting a residual part of the user base. This prioritization is a choice of responsibility: resources allocated where they produce the most value.
If you reported a problem and are not sure if it has been closed, look for the relevant entry in the log or reply to your original ticket. Support can confirm the version in which the fix was implemented.
Recurring bugs
Some categories of problems return periodically because they are linked to external changes: MetaTrader client updates, broker-side changes, browser novelties. The log also notes these cases, so it is possible to reconstruct the evolution of a problem over time. Some of these corrections are accompanied by small dedicated guides in the category Broker, connections and technical operability.
Transparency on limits
No software is bug-free: to declare so would be unrealistic. Our commitment concerns transparency on known issues, the speed of correction of those with the highest impact, and clear communication when needed.
Perimeter
Bug correction concerns technology. Arbicsx provides software pursuant to D.Lgs. 58/1998 (TUF): a technical bug may disturb the platform experience, but it does not change the perimeter of the service, which does not include capital management or financial advice.
How to consult it
The Updates section aggregates resolved bugs, upgrades, and communications. It is not necessary to follow it every day: a periodic reading keeps you updated without weighing you down.
Was this guide helpful?
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