Date of Name Request extension is not reflected properly in Name Examination (NameX) about entity HOT 13 CLOSED

The transaction status of the renewal is "Payment Initialized' as
The payment status is PAID in sbc_pay:

But the payment status hasn't updated in namex.payments table:

The issue can be reproduced in the TEST environment (NR 7687277). The payment status was updated to 'PAID'; however, in namex.payments, the status is still 'CREATED' due to the absence of a namex_pay queue pod in the TEST environment.

from entity.

The following 3 NRs are not in the case because the renewal payments are not complete:

from entity.

In most cases, the payment status is updated in the pay-db. However, if the namex payment queue stopped running (or due to other issues), the payment status was not updated in namex, causing the expiry date not to be updated.

from entity.

Some work related to queue has been done last month by https://app.zenhub.com/workspaces/names-team-board-new-655554cbddd49510027dad2e/issues/gh/bcgov/entity/19490

I wonder if the issue is related?

I picked the latest 50 namex.payment records with payment_status='CREATED', and there are 13 out of 50 sbc-pay.invoices.invoice_status_code = 'PAID' which is inconsistence to what in namex:

"id"	"invoice_status_code"	"created_on"	"payment_date"	"business_identifier"	"payment_method_code"
5513193	"PAID"	"2024-05-23 07:30:55.596998"	"2024-05-23 07:32:04.039998"	"NR 1123292"	"DIRECT_PAY"
5516440	"PAID"	"2024-05-23 17:03:43.583764"	"2024-05-23 17:05:29.109551"	"NR 1359547"	"DIRECT_PAY"
5518413	"PAID"	"2024-05-23 18:54:11.285821"	"2024-05-23 18:54:53.349016"	"NR 4167789"	"DIRECT_PAY"
5519590	"PAID"	"2024-05-23 19:55:26.553389"	"2024-05-23 19:56:19.556562"	"NR 4958058"	"DIRECT_PAY"
5520836	"PAID"	"2024-05-23 21:16:32.127082"	"2024-05-23 21:17:23.517872"	"NR 1487098"	"DIRECT_PAY"
5521482	"PAID"	"2024-05-23 21:48:59.966042"	"2024-05-23 21:50:19.764092"	"NR 0860828"	"DIRECT_PAY"
5521896	"PAID"	"2024-05-23 22:14:32.229578"	"2024-05-23 22:14:50.950092"	"NR 5208234"	"DIRECT_PAY"
5523720	"PAID"	"2024-05-24 02:34:02.247826"	"2024-05-24 02:35:37.997366"	"NR 5977403"	"DIRECT_PAY"
5523973	"PAID"	"2024-05-24 05:29:32.687896"	"2024-05-24 05:30:40.895676"	"NR 1670025"	"DIRECT_PAY"
5525823	"PAID"	"2024-05-24 15:49:21.026468"	"2024-05-24 15:49:48.575233"	"NR 9740303"	"DIRECT_PAY"
5527564	"PAID"	"2024-05-24 17:42:18.522011"	"2024-05-24 17:42:43.386127"	"NR 1664138"	"DIRECT_PAY"
5531925	"PAID"	"2024-05-24 22:03:56.473788"	"2024-05-24 22:04:45.616279"	"NR 0270829"	"DIRECT_PAY"
5532605	"PAID"	"2024-05-24 22:45:53.985027"	"2024-05-24 22:46:22.966034"	"NR 0454058"	"DIRECT_PAY"

from entity.

@bolyachevets could you please take a look?

from entity.

Some work related to queue has been done last month by https://app.zenhub.com/workspaces/names-team-board-new-655554cbddd49510027dad2e/issues/gh/bcgov/entity/19490

I wonder if the issue is related?

I picked the latest 50 namex.payment records with payment_status='CREATED', and there are 13 out of 50 sbc-pay.invoices.invoice_status_code = 'PAID' which is inconsistence to what in namex:

"id"	"invoice_status_code"	"created_on"	"payment_date"	"business_identifier"	"payment_method_code"
5513193	"PAID"	"2024-05-23 07:30:55.596998"	"2024-05-23 07:32:04.039998"	"NR 1123292"	"DIRECT_PAY"
5516440	"PAID"	"2024-05-23 17:03:43.583764"	"2024-05-23 17:05:29.109551"	"NR 1359547"	"DIRECT_PAY"
5518413	"PAID"	"2024-05-23 18:54:11.285821"	"2024-05-23 18:54:53.349016"	"NR 4167789"	"DIRECT_PAY"
5519590	"PAID"	"2024-05-23 19:55:26.553389"	"2024-05-23 19:56:19.556562"	"NR 4958058"	"DIRECT_PAY"
5520836	"PAID"	"2024-05-23 21:16:32.127082"	"2024-05-23 21:17:23.517872"	"NR 1487098"	"DIRECT_PAY"
5521482	"PAID"	"2024-05-23 21:48:59.966042"	"2024-05-23 21:50:19.764092"	"NR 0860828"	"DIRECT_PAY"
5521896	"PAID"	"2024-05-23 22:14:32.229578"	"2024-05-23 22:14:50.950092"	"NR 5208234"	"DIRECT_PAY"
5523720	"PAID"	"2024-05-24 02:34:02.247826"	"2024-05-24 02:35:37.997366"	"NR 5977403"	"DIRECT_PAY"
5523973	"PAID"	"2024-05-24 05:29:32.687896"	"2024-05-24 05:30:40.895676"	"NR 1670025"	"DIRECT_PAY"
5525823	"PAID"	"2024-05-24 15:49:21.026468"	"2024-05-24 15:49:48.575233"	"NR 9740303"	"DIRECT_PAY"
5527564	"PAID"	"2024-05-24 17:42:18.522011"	"2024-05-24 17:42:43.386127"	"NR 1664138"	"DIRECT_PAY"
5531925	"PAID"	"2024-05-24 22:03:56.473788"	"2024-05-24 22:04:45.616279"	"NR 0270829"	"DIRECT_PAY"
5532605	"PAID"	"2024-05-24 22:45:53.985027"	"2024-05-24 22:46:22.966034"	"NR 0454058"	"DIRECT_PAY"

@eve-git This is not related to queue upgrade, as the code has not made it to test/prod. The queue upgrade code is only in dev. But, there is potential for this to be fixed, if NATS queue is the culprit, once we do move with the upgrade to test/prod.

from entity.

@EPortman i will move this to ready for release because we believe it has been fixed in dev/test, after namex api gets pushed to prod, lets verify this is no longer an issue.

from entity.

@ozamani9gh sounds good. I made a reminder to test this later this week.

from entity.

@ozamani9gh I am not able to verify if this has been fixed in Prod? Have we had any examiners confirm that this is still an issue or if it has been remediated with the NameX API release?

from entity.

@EPortman please reach out to @Mihai-QuickSilverDev and confirm this is not happening in prod anymore with the examiners. once done, update ticket and i will close.

from entity.

sent email to Megan and Joshua

from entity.

sent email to Megan and Joshua

from entity.

Will close for now, if issue reappears we can revisit.

from entity.