Resolved: problems with running CPU-intensive automations


We noticed an issue today that some users may have experienced when running CPU-intensive automations. This issue has now been resolved, and a fix applied. Apologies for the inconvenience to those who encountered this.

In the future, please do let us know here in this forum if you experience automations which are consistently stuck in a pending state or run without generating logged output or results. We’ll keep a look out for these, but always appreciate a message here as well.

Happy automating!