Resource group api error: entry not found in cache

[KristapsD]

Describe the bug
I'm getting the following error when trying to provision my teams app: [Solution.ResourceGroupApiError]: Entry not found in cache.
First time provisioning worked Perfectly.

And also receiving the following error when trying to deploy my teams app: [FE.CheckResourceGroupError]: Failed to check resource group existence. Suggestions: Check log for more information. i tried checking the log in Log (extension host) but i didn't find anything regarding teams toolkit there

Realistically i shouldnt even need to provision the app because i havent added any new capabilities, but i still tried it just in case and that was the error i got.

I've already tried remaking the project from a fresh point, that's why i probably could deploy/provision the app yesterday.

To Reproduce
No idea what changed between yesterday and today, when yesterday i could provision and deploy except for the fact yesterday was the first time i did those things and i'm trying to deploy changes today.

Expected behavior
For the Deploy to work without errors

VS Code Extension Information (please complete the following information):

• OS: windows 11
• Version v4.0.5

CLI Information (please complete the following information):

• OS: win 11
• Version 1.1.1

Additional context
Add any other context about the problem here.

[ghost]

Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.

[KristapsD]

A little update - using teamsfx deploy in the VSC terminal worked for now.

[jayzhang]

@KristapsD Thanks for reporting.

The root cause is somehow from azure-account extension:
microsoft/vscode-azure-account#53

As a workaround you could try signing out and signing back in to your Azure Account using the command palette. (microsoft/vscode-azurefunctions#1264)

Then you can re-try again.

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

[kbrkelsi]

I have this same issue, the workaround does not work for me. I open a CloudShell bash window after ensuring my Edge profile with my Azure tenant is active and pick my Azure account, it immediately gives me this error. I have never been able to successfully use this and it happens consistently. Please do not close this issue. I would be happy to give feedback for you to be able to resolve this.

[jayzhang]

I have this same issue, the workaround does not work for me. I open a CloudShell bash window after ensuring my Edge profile with my Azure tenant is active and pick my Azure account, it immediately gives me this error. I have never been able to successfully use this and it happens consistently. Please do not close this issue. I would be happy to give feedback for you to be able to resolve this.

Thanks @kbrkelsi

[KristapsD]

@KristapsD Thanks for reporting.

The root cause is somehow from azure-account extension:
microsoft/vscode-azure-account#53

As a workaround you could try signing out and signing back in to your Azure Account using the command palette. (microsoft/vscode-azurefunctions#1264)

Then you can re-try again.

Just tested, this workaround worked for me. Allowed me to provision and deploy to a new env.

[kbrkelsi]

Sorry, yes, I realize what project I'm under now, I'll make sure this is known in Azure Account. Thanks!