We've seen no further issues with workflow triggers from the Iterable platform, so we're going to close this incident. As always, we appreciate everyone's patience, and encourage you to connect with us via support@iterable.com should you see anything unusual with your workflows.
Posted Oct 27, 2018 - 18:27 PDT
Monitoring
Our team is still looking into the proper reproduction of the issue at hand, and has extended logging to capture additional information. In the meantime we will be closely monitoring the situation. This has only impacted a small subset of customers that we are aware of, but if you notice any behavior of workflows not being triggered properly please reach out to support@iterable.com.
Posted Oct 27, 2018 - 04:13 PDT
Update
We have determined that the impact of this issue is extremely minimal. The engineering team is still working to find a consistent reproduction scenario. Next update will be 4am Pacific Time or when the incident moves to a new status.
Posted Oct 26, 2018 - 21:03 PDT
Update
We're still working on finding root cause, but we can confirm that this impact is limited only to workflows that are triggered by custom events. We're analyzing an additional level of logging and working directly with some affected customers. Next update by 9pm Pacific Time.
Posted Oct 26, 2018 - 19:46 PDT
Investigating
We are looking into reports of sporadic and intermittent situations in which workflows are not triggering for a very small number of customers. Our engineers are actively investigating. We'll update again at 7:45pm Pacific Time