Objective

Understand how Valix communicates and deprecates features so you can plan migrations confidently.

Prerequisites

Step-by-Step Instructions

1. 1

   Our commitment: We never ship breaking changes without at least 30 days' notice.

2. 2

   How we notify you: Breaking changes are announced via (1) an in-app banner at the top of your dashboard, (2) an email to all company admins, and (3) a prominent entry on the Release Notes page.

3. 3

   What counts as a breaking change:

   • —Removing or renaming a user-facing feature
   • —Changing the shape of a webhook or API response
   • —Deprecating a user role or permission
   • —Moving data to a new schema that requires action on your part
4. 4

   What does NOT count: Bug fixes, UI refreshes, new optional features, performance improvements.

5. 5

   If you need help adapting to a breaking change, contact support via the Support page.

Troubleshooting Tips