Blog Post
We understand the concern on all fronts here. As with the other item above, the single most difficult part of our job is prioritization. What many people consider tablestakes, others might consider "too cumbersome" or even a bug. Development on Automations has far from stopped. In fact, we have been very vocal about where we misstepped with Automations, and how we corrected for it. What you experienced was a plethora of features that were used quicker than we ever expected. That required us to slow down on development of features, and focus on stability, performance and scale. We have two teams right now working on Automations.
We don't have immediate plans to increase the frequency of Automations or Subscriptions. We walk a fine line with offering these capabilities and also balancing things like performance and how applications scale. It is important to us that we don't just release more capabilities into the wild that could adversely impact an app.
We don't have immediate plans to increase the frequency of Automations or Subscriptions. We walk a fine line with offering these capabilities and also balancing things like performance and how applications scale. It is important to us that we don't just release more capabilities into the wild that could adversely impact an app.