Starting about two weeks ago, all scheduled requests started triggering more than one time per scheduled occurrence. Sometimes they trigger as many as six times per scheduled occurrence. This creates a mess of duplicate incidents that have to be manually cleaned up. No changes were made to the schedules or requests. I have an active support ticket opened for this issue and it has been acknowledged by SWSD support that this is a bug that was introduced by the engineering team, and that they are working to resolve it. I hope this post brings some attention to the issue because it is not being resolved in what I would consider a timely manner. It's generally a good practice to have a rollback plan for how to undo a change/update when you break something.