Lex rebuild is failing due to 'QnAIntent' being considered a built-in intent name about qnabot-on-aws HOT 8 CLOSED

Hi @cristi-constantin - thanks for reporting the issue. I also noticed that our test deployments in us-east-1 and ap-southeast-2 failed last night due to the same reason. Curiously, similar deployments in other regions did not. Let us look into this and get back to you.

from qnabot-on-aws.

I'm also running into this when trying to spin up a new stack. Is there currently a workaround?

from qnabot-on-aws.

There is currently no workaround. If you are spinning up a new stack and the region doesn't matter to you, the only impacted regions are us-east-1 and ap-southeast-2, so you should be able to deploy in us-west-2 for example.

from qnabot-on-aws.

Unfortunately we can only spin it up on us-east-1. Do you have a sense of when this will work again?

from qnabot-on-aws.

We're actively working on this but, unfortunately, I cannot commit to a timeline. We're treating this as high priority so we should have an update soon.

from qnabot-on-aws.

@cristi-constantin @hablat - the issue should be resolved now. Our builds are passing in all regions. Please try again. Let us know if your issue has not been resolved.

from qnabot-on-aws.

@marcburnie - confirmed as resolved.

from qnabot-on-aws.

@marcburnie Thank you, its working for on creation for me as well.

from qnabot-on-aws.