This post describes one way to resolve a problem, where you receive an error like “The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.” when calling your Azure Functions.
Another day, another simple, yet kind of weird issue to solve! This time I was developing a simple Azure Function to access Microsoft Graph API. This particular issue was kind of bugging, since the error message actually had nothing to do with the actual issue and gave no pointers as to how to fix the issue!
I was just developing a function, and suddenly it stopped working, and the only error message I got was this:
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
In client-side code, if called with $.get(), it looks somewhat like this:
So, what did I do to cause this?
Steps to reproduce:
For me, this is the way I caused the error.
- Create an Azure Function that takes in GET argument(s) using the beta version of the CLI (2.1, in my case)
- Call the function from any other source, passing arguments of varying length
- Suddenly you notice, with quite a few different arguments, you only get this error from the Azure function: “The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.” It doesn’t happen with all arguments, though!
- When the issue is underway, even if you attach the remote debugger to your Azure Function, it won’t fire, at all – so debugging is kind of difficult!
But what on Earth causes this?