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

NRA/Namex Issue: a client's payment for priority upgrade being successful, however it did not reflect in NAMEX #19052

Closed
eve-git opened this issue Dec 15, 2023 · 8 comments
Assignees
Labels
bug Something isn't working Names Team Name Request Name Examination Team NameX NameX and related services proxied via namex Priority1

Comments

@eve-git
Copy link
Collaborator

eve-git commented Dec 15, 2023

We've encountered a new instance of a client's payment for priority upgrade being successful, however it did not reflect in NAMEX.

The "requests.priority_cd" field was initially set to 'Y' upon completion of the payment. Nevertheless, it was subsequently reverted to 'N' following the execution of the NRO batch job.
image.png

More details please reference to https://github.com/bcgov-registries/ops-support/issues/3149

@eve-git eve-git added bug Something isn't working Names Team Name Request Name Examination Team NameX NameX and related services proxied via namex labels Dec 15, 2023
@Rajandeep98 Rajandeep98 self-assigned this Dec 28, 2023
@Rajandeep98
Copy link
Collaborator

fix applied: bcgov/namex#1507

@Rajandeep98
Copy link
Collaborator

pending validation

@oanyahuru
Copy link
Collaborator

I tested and the issue appears resolved. The issue appears to be related to #18961. I am moving this along

@iamjtodd iamjtodd closed this as completed Jan 4, 2024
@iamjtodd iamjtodd reopened this Jan 5, 2024
@iamjtodd
Copy link
Collaborator

iamjtodd commented Jan 5, 2024

Reopening as another instance has been reported by a client:

image.png

image.png

@iamjtodd
Copy link
Collaborator

iamjtodd commented Jan 8, 2024

Received email from client regarding NR4875536:

Client upgrade to priority on Dec. 27th which was not reflected in NAMEX. Then they attempted to upgrade again on Jan. 2 which was also not reflected in NAMEX. (Paid for priority upgrade twice). As these are PAD payments could someone please process a refund for the 2 priority payments as our examination time did not meet the 48 hour deadline for Priority service.

Further, it should not be possible for a client to pay for Priority upgrade twice.

@iamjtodd
Copy link
Collaborator

iamjtodd commented Jan 8, 2024

Additionally, NR 1112814 was upgrade to Priority on January 3 but did not reflect in NAMEX. As this is a PAD payment could a refund please be issued as our examination did not meet the Priority service deadline.

@Rajandeep98
Copy link
Collaborator

hi @iamjtodd ,
I tested to check on priority flip in dev and test they look fine ,
for this particular NR, I saw the very first time change of priority occurred on 3rd Jan, and we pushed the fix on 4th Jan morning , the priority already was flipped at that time.
image.png

@iamjtodd
Copy link
Collaborator

iamjtodd commented Jan 9, 2024

@Rajandeep98 for NR4875536 and NR1112814 it does show the upgrade to priority log in transaction history, however it didn't actually push the NR through to Priority. (Usually the NR text changes to Red and there is a Red star and it will say "PRIORITY".

Example of successful Priority NR
image.png
NR4875536
image.png

NR1112814
image.png

@PCC199 PCC199 closed this as completed Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Names Team Name Request Name Examination Team NameX NameX and related services proxied via namex Priority1
Projects
None yet
Development

No branches or pull requests

6 participants