Automations: when this happens, do that — Good to know

• Email steps need the server's email service (Mandrill) configured, and the Generate with AI step needs an AI model configured — without them, those steps fail with a clear message. • A scheduled automation with a table chosen fires once per matching record, capped at 100 records per fire. • Steps run top to bottom and stop at the first failure — later steps are skipped and the run is marked Failed or Partly failed. • Automation chains are guarded at 3 levels deep: past that, the loop guard stops the chain and logs a Skipped run. • Run history is kept for 90 days, so older runs age out of the log. • A numeric increase/decrease is applied straight to the database, so it does not itself trigger other automations — a “low stock” rule won't fire off a decrement.