Open riyazuddinsyed opened 3 years ago
Two potential issues:
1) Temporary ID for IA isn't going away in MB dashboard after incorporation - 1 day 2) NR not being consumed - see 6033
This could potentially result in further work around consuming the NR.
@kzdev420 Kevin, do you have what you need to work on this ticket?
Hi @Mihai-QuickSilverDev @riyazuddinsyed
First, I need to reproduce the issue locally. I want you guys to help me with that.
Where is the Mint corps
?
Hi @riyazuddinsyed
This is the error you are seeing for this task? Private Zenhub Image
It may still be possible to have a race condition, as the NR is not marked as consumed until the Filer processes it, which could be up to 2 weeks in the future (future effective IA). During this time, another IA could probably be filed with the same NR.
I suspect only the first IA to consume the NR will succeed and the others will fail... Kevin will test this per Jason's comments above.
Is it possible to mark the NR as consumed as soon as it is payed for?
As soon as the IA is paid for? Hmm, maybe.
@vysakh-menon-aot , which component handles the payment right now? The same component that checks the NR state?
And what would we do if a future effective IA fails to be completed (by the Filer)? I guess we'd have to refund them and reset the NR?
entity-pay (queue) mark a filing as paid once it receive confirmation.
Thanks. And how is entity-pay triggered to process the payment? Is it as soon as the filing is submitted, or when the Filer processes it?
entity-pay receive a notification from pay-api (or one of the queue in pay) if the payment is processed successfully (right after a filing is submitted).
OK, that's good news. Would it make sense, and would it be easy, to mark a NR as consumed as soon as pay succeeds (right after a filing is submitted)?
It is possible. We need to confirm this with business and @thorwolpert
In the first account, NR was converted into a Business.
In the second account, I was not able to Resume the Draft and got an error
Invalid Incorporation Application. An unexpected error has occurred. ...
So, I reloaded the page, and after refreshing the page, NR was not shown.
It is possible. We need to confirm this with business and @thorwolpert
@Mihai-QuickSilverDev Can you help with this, please?
In the first account, NR was converted into a Business.
In the second account, I was not able to Resume the Draft and got an error
Invalid Incorporation Application. An unexpected error has occurred. ...
So, I reloaded the page, and after refreshing the page, NR was not shown.
What does the second IA look like on My Business Registry page?
Can you show the page without the NR please?
Hi @severinbeauvais
https://dev.account.bcregistry.gov.bc.ca/account/2079/business
BCREGA001/98900001
NR was NR 6856351
This is not ready to work on, we need business input for how this will go.
Kevin, please try this:
@thorwolpert Question for you: Could we mark the NR Consumed as soon as the client clicks File and Pay, or do we need to wait until the filing is complete? - This would apply to Future Effective Date filings. We are trying to prevent the NR being used by another IA, while waiting on an FED for the first IA.
@PCC199 ticket is in backlog on entities team. Just on our board for visibility
@Mihai-QuickSilverDev This ticket has been well investigated and we are waiting for guidance from Thor on whether it is acceptable to mark the NR as consumed as soon as payment is confirmed (instead of after the IA is processed by the Filer, which could be 2 weeks in the future). If this is OK then the risk of using the same NR for 2 different IAs is very small -- the time between filing an IA and paying for it (pay queue issues notwithstanding). From a business point of view, is that an acceptable risk?
This is the same issue as 21698.
Describe the bug in the current situation
When a user Affiliates the NR, then the user is able to file more than one Incorporation Application thereby getting multiple BC Benefit Companies
Impact of this bug All users affiliating the NR
Steps to reproduce the behavior: