We have identified an interruption to scheduled actions from August 18th at 11:13 UTC to August 19th at 08:08 UTC. This issue impacted a small number of customers on legacy licenses. The issue was resolved on August 19th at 08:08 UTC. We have found the cause and impact of this issue. A code change related to how we check if a scheduled action should be executed. We altered how we confirm that the scheduled action exists in a "published" story. Customers on legacy license plans do not have the ability to publish/unpublish stories, and as a result, we skipped the execution of those scheduled actions. To mitigate the risk of this issue recurring, we will centralize all checks of story published state to ensure it always takes legacy license models into account. We are reaching out directly to those customers affected. Thank you for your patience as we resolved this issue.