# Tag intermittency

**URL:** <https://forum.inductiveautomation.com/t/tag-intermittency/51030>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [September 16, 2021, 7:25am UTC](https://forum.inductiveautomation.com/t/tag-intermittency/51030 "2021-09-16T07:25:15Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 17, 2021, 1:34pm UTC](https://forum.inductiveautomation.com/t/tag-intermittency/51030/18 "2021-09-17T13:34:08Z")

</div>

Also check the message servicing and comms servicing rate limiting bits in the SLC status file:

> [@Typical Performance between Ignition and AB SLC 5/05](https://forum.inductiveautomation.com/t/typical-performance-between-ignition-and-ab-slc-5-05/17262/3):
>
> Check “Comms Servicing Selection” and “MSG Servicing Selection” for channel 1 (S:2/15 & S:33/7). If either is set, it will crush your throughput, as only one request will be processed per scan (Comms) or per certain control flow instructions (MSG).

---

_[View the full topic](https://forum.inductiveautomation.com/t/tag-intermittency/51030)._