Skip to content Start from ₹499/year for your first year
Contact us
Nothing fits?
Build a custom pack

Pick modules, wire your own actions and automations. Live in two weeks.

  • Modules The screens your trade needs, switched on.
  • Your words Customers, orders and bills called what you call them.
  • Automations Reminders and follow-ups that run by themselves.
For example
Laundry & dry cleaning
Order Laundry ticket
Talk to us about yours Browse all 32 packs →
ERP packs
Classes & coaching Corporate training Schools & colleges Clinics Diagnostic lab / pathology Vet clinic & pet shop Contractors & site projects Event & wedding planner Gym & coaching Professional practice Property broker Rental & hire Repairs & field service Salon & spa Security & manpower agency Services & appointments Travel agency & tour operator Website Bakery & sweet shop Caterer & tiffin service E-commerce Hotel / guest house PG & student housing Restaurant Shops & counters Association & club Exporter Farmer producer organisation Housing society & RWA Manufacturing Trusts & non-profits Wholesale & building materials
Modules Pricing Desktop & mobile apps Documentation Blog Partners About
Contact us Sign in
Theme

Reading the run log

What an automation did, when it did it, and why it failed when it failed.

Automations Updated 14 September 2026 · 3 min read · Requires: Owner or Admin role

Each automation's row on Workspace → Automations shows how many times it has run and when it last ran. View runs opens its 20 most recent runs, newest first.

What counts as a run

A run is recorded each time the event happened and every condition held - each time the automation actually acted. An event whose conditions did not match leaves nothing behind, so a rule that never matches shows no runs at all.

OK and Failed

A run is OK when every action succeeded. It is Failed when at least one did not, and its message is the first failure's reason. The other actions on that run still ran.

Common failures

  • Webhook URL was blocked - the address resolves to a private or internal network. A webhook can reach only public addresses, over http or https.
  • Webhook responded with HTTP … - the receiving system refused or failed. A webhook waits five seconds at most, does not follow redirects and is not retried.
  • Needs add-ons this workspace no longer has - a payment-link action whose add-on has since been switched off.

A rule on an event from a module you have since switched off stops running altogether. It leaves no failed runs, because it no longer runs.

Was this page useful? You will be asked to log in first.
← Previous
Testing a rule safely
Next →
Roles, permissions & approvals