# ignition.ScheduleManager Spamming GW Logs

**URL:** <https://forum.inductiveautomation.com/t/ignition-schedulemanager-spamming-gw-logs/74789>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [June 8, 2023, 7:10pm UTC](https://forum.inductiveautomation.com/t/ignition-schedulemanager-spamming-gw-logs/74789 "2023-06-08T19:10:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pablo\_David](https://avatars.discourse-cdn.com/v4/letter/p/5daacb/32.png) [@Pablo\_David](https://forum.inductiveautomation.com/u/Pablo_David)\
**Post date:** [June 8, 2023, 7:10pm UTC](https://forum.inductiveautomation.com/t/ignition-schedulemanager-spamming-gw-logs/74789/1 "2023-06-08T19:10:53Z")

</div>

The title is self-explanatory; every 3-10 seconds, my logs are spammed with **[E] ScheduleManager. Attempt to check for schedule for "NAME," Which doesn't exist**

I've run out of ideas to disable this, but now it's nearly impossible to read logs as its flooding the dump files.

Has anyone else had a similar issue?

---

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [June 8, 2023, 7:27pm UTC](https://forum.inductiveautomation.com/t/ignition-schedulemanager-spamming-gw-logs/74789/2 "2023-06-08T19:27:48Z")

</div>

Do you have any Alarm Notification Profiles that might be referencing the `NAME` schedule? Double check that your _Config-\>Alarming-\>Schedules_ (in the gateway web UI) are defined as expected, and that the users in your user source are pointed at schedules that exist.

---

<div class="post-metadata">

**Author:** ![Pablo\_David](https://avatars.discourse-cdn.com/v4/letter/p/5daacb/32.png) [@Pablo\_David](https://forum.inductiveautomation.com/u/Pablo_David)\
**Post date:** [June 9, 2023, 12:04pm UTC](https://forum.inductiveautomation.com/t/ignition-schedulemanager-spamming-gw-logs/74789/3 "2023-06-09T12:04:17Z")

</div>

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/f/ffde303d1898b829f8f690c7510c3a2516c852ef.png)

Here is a copy of the Schedules, we use to have all the schedules in here but we werent using them. However, when we did have them, they too would spam the logs. Below is a photo of the logs being spammed.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/0/c08aae3ffba32b7f48ff89a9d280e3ef4c59b42c.png)

---

<div class="post-metadata">

**Author:** ![Pablo\_David](https://avatars.discourse-cdn.com/v4/letter/p/5daacb/32.png) [@Pablo\_David](https://forum.inductiveautomation.com/u/Pablo_David)\
**Post date:** [June 9, 2023, 12:08pm UTC](https://forum.inductiveautomation.com/t/ignition-schedulemanager-spamming-gw-logs/74789/4 "2023-06-09T12:08:07Z")

</div>

[SOLVED] The error was appearing because after the schedule was deleted, there were still users assigned that schedule which was causing the issues.