# S4261 // Methods should be named according to their synchronicities should not apply to controllers **URL:** \ **Category:** Report False-positive / False-negative...\ **Tags:** csharp\ **Created:** [September 10, 2018, 2:28pm UTC](https://community.sonarsource.com/t/s4261-methods-should-be-named-according-to-their-synchronicities-should-not-apply-to-controllers/2436 "2018-09-10T14:28:05Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![paulhickman](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/paulhickman/32/2334_2.png) [@paulhickman](https://community.sonarsource.com/u/paulhickman)\ **Post date:** [September 10, 2018, 2:28pm UTC](https://community.sonarsource.com/t/s4261-methods-should-be-named-according-to-their-synchronicities-should-not-apply-to-controllers/2436/1 "2018-09-10T14:28:05Z")
Version 7.5.0.660 Rule S4261 suggests method Xyz should renamed to XyzAsync if it is an async method. This rule should be suppressed for any public method on a class that derives from the MVC Controller base class, as this may interfere with routing. ---
**Author:** ![Val](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/val/32/98_2.png) [@Val](https://community.sonarsource.com/u/Val)\ **Post date:** [September 24, 2018, 8:47am UTC](https://community.sonarsource.com/t/s4261-methods-should-be-named-according-to-their-synchronicities-should-not-apply-to-controllers/2436/2 "2018-09-24T08:47:02Z")
Hi @paulhickman, indeed you are right, it seems that the MVC controller routing breaks when you change, but Web API controllers handle the Async suffix just fine (I tested with an [ASP.NET](http://ASP.NET) Core Web Application)… I created a ticket to investigate what should be done, because it seems the exception from the rule could be a bit more complex. [https://github.com/SonarSource/sonar-csharp/issues/1875](https://github.com/SonarSource/sonar-csharp/issues/1875)