-
Notifications
You must be signed in to change notification settings - Fork 59
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
Comments
fix applied: bcgov/namex#1507 |
pending validation |
I tested and the issue appears resolved. The issue appears to be related to #18961. I am moving this along |
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. |
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. |
hi @iamjtodd , |
@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". |
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.

More details please reference to https://github.com/bcgov-registries/ops-support/issues/3149
The text was updated successfully, but these errors were encountered: