Shortly after we shipped Email Automation, a user reported that their auto-reply rule was not running. After investigating, we found two bugs — one that silently blocked the entire email automation process, and one that caused misconfigured rules to fail without any feedback.

What went wrong

Bug 1 — Email automation was skipped when Kule had nothing else to do. Email automation runs as part of the proactive agent cycle, which fires hourly. If Kule had no pending tasks or goals to action that hour, the cycle exited early before ever reaching the email automation step. This meant that users whose AI Colleague was otherwise idle would never have their email rules processed — even if new emails were waiting.

Bug 2 — Auto-reply rules with a missing reply template failed silently. If a rule was created with the auto-reply action but without a reply template, the rule would be skipped with no warning or log entry visible to the user. The action was recorded internally as a failure, but nothing surfaced to explain why.

What we fixed

Email automation now runs every proactive cycle regardless of whether Kule has other tasks to handle. It no longer depends on the proactive agent having something to do first.
Auto-reply rules with no reply template now log a clear warning in the activity log, making it easy to spot and fix misconfigured rules.
When email automation handles emails and the proactive agent is otherwise idle, Kule will still send you a push notification summarising what was handled.

What you should do

No action is required. The fix is live and your email automation rules will now run on the next hourly cycle. If you have an auto-reply rule and it is not triggering, check that a reply template has been set on the rule — Kule will now flag this clearly if it is missing.

We apologise for the disruption and thank the user who reported this. If you notice anything else behaving unexpectedly, please reach out via the in-app chat.