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
Describe the bug
Since the latest 1.16.0 release (but may not be related to the version this way) when I start up a new Lago instance (with multiple already existing customers) everything seems fine until I want to create a new customer.
Once, I try to create a new customer through the API (which may related to the timing after the startup, based on its a ratelimit error) the customer creation fails with Valvat::RateLimitError. Some time later I can create the customer without any problem.
To Reproduce
Steps to reproduce the behavior:
Make several VAT checks (I think the startup process may check the existing customers or something)
After that instantly try to create customers through the API
Valvat::RateLimitError should throw a 500 error on the customer endpoint
Expected behavior
The VAT check should not be a sync process, instead it should run in the background and should not interfere with the customer creation endpoint.
We are aware of it but thanks for catching it!
It's actually a sync call because some users may create invoice directly just after the customer, it may lead to bad VAT being applied (or no VAT at all).
As a very quick fix I would recommend you to catch this error and retry this call when you have this error.
Describe the bug
Since the latest 1.16.0 release (but may not be related to the version this way) when I start up a new Lago instance (with multiple already existing customers) everything seems fine until I want to create a new customer.
Once, I try to create a new customer through the API (which may related to the timing after the startup, based on its a ratelimit error) the customer creation fails with
Valvat::RateLimitError
. Some time later I can create the customer without any problem.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The VAT check should not be a sync process, instead it should run in the background and should not interfere with the customer creation endpoint.
Additional context
Version
The text was updated successfully, but these errors were encountered: