title: Does Azure Function method name matter?
body: <p>I am currently developing some C# Azure Functions. The naming convention I use is <code>Process[ThingIWantToProcess]()</code> like so...</p>
  
  <pre><code>public static void ProcessRequest([TimerTrigger("00:00:10", RunOnStartup = true, UseMonitor = false)] TimerInfo timer, ILogger logger)
  {
       // Do function things
  }
  </code></pre>
  
  <p>A few days ago, all of the functions (currently, 6 of them) stopped running when they were deployed, but no code had been changed that I am aware of or can see.</p>
  
  <p>The console, both locally and the Kudu console, say "Found the following functions:" and display all the expected functions; however, those functions are never run.</p>
  
  <p>I tried all sorts of things, including re-deploys, restarting the Azure Web Job, and changing the contents of the methods, but still nothing fired. And then, I changed the name of the function, and suddenly it started working!</p>
  
  <p>So instead of <code>ProcessRequest</code> it was now <code>ProcessRequest1</code>, and the function fired successfully. I changed the name several different ways, and all of them worked, but when I changed back to <code>ProcessRequest</code>, it stopped working again.</p>
  
  <p>I can't find anything explaining this behavior in the docs or internet search, and I'm concerned it will happen again during future maintenance.</p>
  
  <p><strong>Has anyone else experienced this, and if so, can you point me to some kind of explanation?</strong></p>