Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(VAT ID Check): avoid re-checking Invalid Input #51

Merged
merged 1 commit into from
Oct 24, 2024

Conversation

barredterra
Copy link
Member

@barredterra barredterra commented Oct 24, 2024

If a VAT ID Check resulted in an "Invalid Input" status, new cheks would get created on every run, with the input not becoming any more valid. Now we wait for 3 months before checking again.

If a VAT ID Check resulted in an "Invalid Input" status, new cheks would get created on every run, with the input not becoming any more valid. Now we wait for 3 months before checking again.
@barredterra barredterra merged commit 1264d67 into version-15 Oct 24, 2024
1 check passed
@barredterra barredterra deleted the vat-invalid-input branch October 24, 2024 15:59
@barredterra
Copy link
Member Author

@Mergifyio backport version-14

Copy link
Contributor

mergify bot commented Oct 24, 2024

backport version-14

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Oct 24, 2024
barredterra added a commit that referenced this pull request Oct 24, 2024
Co-authored-by: Raffael Meyer <14891507+barredterra@users.noreply.github.com>
barredterra pushed a commit to 0xD0M1M0/erpnext_germany that referenced this pull request Oct 24, 2024
# [15.6.0](alyf-de/erpnext_germany@v15.5.0...v15.6.0) (2024-10-24)

### Bug Fixes

* **VAT ID Check:** avoid re-checking Invalid Input ([alyf-de#51](alyf-de#51)) ([1264d67](alyf-de@1264d67))

### Features

* add workspace ([alyf-de#52](alyf-de#52)) ([87f4fe4](alyf-de@87f4fe4))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant