Known bugs and updates

The Arbicsx platform is in continuous evolution. Each new version can bring improvements, fixes for known bugs and, occasionally, new behaviors to keep in mind. This guide explains where you find official information and how to proceed when you encounter an anomalous behavior.

Where updates and known bugs are published

The official source is the category Updates, releases and maintenance. Here you will find:

• release notes for new versions;
• list of known bugs with resolution status;
• scheduled maintenance notices;
• technical communication relevant to the user.

Consulting this category is the first thing to do when a platform behavior seems strange: it is often already tracked with the relative explanation or temporary solution.

How the platform behaves during updates

Important updates are typically communicated in advance. During the release, short windows may occur where some features are degraded or unavailable. Scheduled maintenance follows the same principle: the platform signals the start time and estimated end time.

If you found a bug not yet reported

If the anomalous behavior you are observing does not appear among the known bugs, reporting it is valuable. Open a ticket from support describing accurately:

• how to reproduce the problem, step by step;
• what you expected compared to what you saw;
• browser, device, time, any screenshots;
• frequency (isolated, recurring, systematic).

The technical team evaluates the report, classifies it and, when the bug is confirmed, adds it to the official list with the processing status.

Minor vs major updates

Not all updates have the same impact:

• Minor updates: fixes and small improvements, invisible in daily use.
• Major updates: changes that can modify layout, features or metrics, always communicated in advance.

After a major update, it is normal to notice some differences in the interface. If a function seems missing, before considering it a bug, check the release note to see if it has been moved or renamed.

Why the list of known bugs is public

Publishing known bugs is not a sign of weakness, it is an act of transparency. Every software platform lives with imperfections that are progressively resolved. Seeing an updated list helps users distinguish what is already tracked — and therefore in progress — from what would be useful to report as new.

If you recognize yourself in a bug already known, there is no need to open a new ticket: optionally add information through the channels indicated in the official communication. If instead you recognize a behavior not described, your report has concrete value.

How to contribute with quality

• Consult the public list of known bugs first.
• Report only behaviors not yet tracked.
• Provide detailed technical context.

Service continuity

The platform is designed to guarantee continuity even during updates. In rare cases where a window of unavailability is inevitable, it is announced in advance. If during an update you encounter an unexpected error, consult the updates first and then, if necessary, contact support.