# Alarm Names Allow Forward Slashes **URL:** \ **Category:** Ignition Early Access\ **Created:** [May 12, 2020, 5:26pm UTC](https://forum.inductiveautomation.com/t/alarm-names-allow-forward-slashes/34663 "2020-05-12T17:26:24Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [April 4, 2022, 5:29am UTC](https://forum.inductiveautomation.com/t/alarm-names-allow-forward-slashes/34663/3 "2022-04-04T05:29:04Z")
FYI I just added another topic RE this. Personally I think it's a bug and that alarm names with slashes and commas should not be allowed, as these have consequences especially when trying to read/write to them via scripting functions. > [@\[BUG/FEATURE\] Disallow commas and slashes in alarm names](https://forum.inductiveautomation.com/t/bug-feature-disallow-commas-and-slashes-in-alarm-names/57985): > > v8.1.5 Not sure if this is fixed already, but someone added some alarms into my project and put commas and slashes into the alarm names which is obviously bad and caused issues. Can the alarm name field please do some input parsing to stop illegal characters from making it into this field? Specifically, the issue is that you can’t use script to read these alarms. E.g.: system.tag.readBlocking('Alarms/Stuff Broke Check Something/Alarms/Stuff Broke, Check Something.Priority') \>\>ValueError: I… --- _[View the full topic](https://forum.inductiveautomation.com/t/alarm-names-allow-forward-slashes/34663)._