You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately being a victim of success, VIES is frequently overloaded returning the error message MS_MAX_CONCURRENT_REQ which fails the query, failing the operation.
It would be nice to be able to 'tag' the fact that a VIES check is demanded if the interactive query fails, and eventually schedule a CRON job to retry after some interval of time.
recently it is for the most part impossible to use this function, please upgrade from enhancement to bug
it should therefore be optional (by default) to do the VIES validation.
In any event, if base_vat is installed, env.company.vat_check_vies should be respected, or at least this value should be used as the default value of an eventual option specifying to do a synchronous VIES check.
There are two different levels of VAT number validation:
--------------------------------------------------------
* By default, a simple off-line check is performed using the known validation
rules for the country, usually a simple check digit. This is quick and
always available, but allows numbers that are perhaps not truly allocated,
or not valid anymore.
* When the "VAT VIES Check" option is enabled (in the configuration of the user's
Company), VAT numbers will be instead submitted to the online EU VIES
database, which will truly verify that the number is valid and currently
allocated to a EU company. This is a little bit slower than the simple
off-line check, requires an Internet connection, and may not be available
all the time. If the service is not available or does not support the
requested country (e.g. for non-EU countries), a simple check will be performed
instead.
Unfortunately being a victim of success, VIES is frequently overloaded returning the error message MS_MAX_CONCURRENT_REQ which fails the query, failing the operation.
It would be nice to be able to 'tag' the fact that a VIES check is demanded if the interactive query fails, and eventually schedule a CRON job to retry after some interval of time.
https://stackoverflow.com/questions/74821299/ms-max-concurrent-req-vies-vat-validation
Then, at least, if one is creating a record, the effort isn't totally lost.
The text was updated successfully, but these errors were encountered: