Elbuz logs each rule command in the “Operation log” and flags diagram rules with no condition, no actions or a possible loop, so you spot a mistake before hundreds of emails go out.
When you need this:
- The rule is on, but no email arrives — the log shows if the command ran and why it failed.
- Enabling a rule for all records — first test it on one document with a narrow condition.
- The mail server rejects rule emails — after three failures, sending pauses.
- The rule already did damage — unpost documents, trash extra contacts.
Where to start: “Automatic rules” → “Rules diagram” in the header.
What helps you test a rule
- “Rules diagram” — a graph of all rules with warnings about an empty condition, disabled actions and a possible loop.
- “Operation log” — one line per command run, with “Failed!” and the reason next to it.
- Email pause — after three failures in a row, no email is sent for the record until you fix the template or the mailbox.
- Risky spots — a loop, mass firing during import, several rules on one event.
- Interrupted run — what stays done and what happens when you save again.
- Cleaning up — unposting, extra contacts and organizations.
Rules diagram: three warnings
The window header has a “Rules diagram” button. It draws a graph of everything you have set up: event → rule with a condition → commands in order. The diagram is view-only; to edit a rule, click the pencil in the corner of its block.
At the top there is an “Area” filter with “All rules”, “Documents”, “Contacts” and “Companies” (the last one is always empty: you can't create rules for this area in the interface), an “Enabled only” checkbox and a “Rules: … · enabled: … · actions: …” counter.
1
Event block2
Rule block with condition3
Action block- Event block — every rule for this event starts here.
- Rule block — the condition is written under the name in plain words.
- Action block — actions are chained in execution order.
The key part is three warnings the app adds by itself. It's a ready-made self-check, faster than opening each rule one by one.
| Label on the block | What it means |
|---|---|
| “No condition — fires on every event” | the rule is enabled but the condition is empty: the commands run for every document or contact without exception |
| “All actions are disabled — the rule does nothing” | the rule is enabled but has no enabled command |
| “Changes the same record it listens to — possible loop” | the rule listens to a document event and itself changes the document (or the same with a contact) |
Smaller details are visible there too: the rule block shows the condition in plain words or “No condition — fires on every event”, and the command block shows the email template name or “No mail template selected”, the flow name or “No flow selected”.
If several rules hang on one event, it is labeled “Rules on this event: N” — a reminder that all of them will fire, one after another.
Where to see that a rule fired
Every command run leaves a line in the “Operation log”, which you open from the “Account” → “Operation log” menu. The line looks like this:
“Trigger #7 заказ - статус - в обработке Run a command: #8 Send mail”
That is: rule number, rule name, command number, command name. If the command failed, “Failed!” is added in front and the line is highlighted as an error:
“Failed! Trigger #7 заказ - статус - в обработке Run a command: #8 Send mail”
1
Operation subtype2
Trigger run line- Operation subtype — the filter is set to Trigger, so only rule runs are listed.
- Info — each line names the rule and the command it executed.
Look for the reason in neighboring log lines from the same moment. For an email it is a separate “Email not sent!” entry with the address, subject and mail server error, or “No email provided!” if the recipient in the template is empty.
An empty log means something else: the command never ran. Either the condition wasn't met, or this command had already run for this record.
Email fails three times — pause
If a trigger email fails for the same record three times, the app stops trying: “The email failed 3 times in a row — sending for this record is paused until the email template or mailbox is changed.” is added to the “Failed!” line. That way a broken mailbox doesn't flood the log with hundreds of identical errors.
The pause lifts by itself as soon as you save this command's email template or any mailbox: next time the email will try to go out again.
“My Day” on the desktop shows the “Trigger emails are not being sent” alert with the rule name and last error (to users with access to the triggers window). A click opens the place to fix it: “Email templates” for a template error, or “Connect mailbox” for a problem with the server, login, password or sender address.
Risky spots
Loop
A rule listens to “Document: update” and uses “Change document data” to edit the same document. This raises no new event: every command that changes or creates something marks its own edit with an internal flag, and the app ignores it. The same goes for posting: a command that posts a document doesn't raise the “Document: post (sign)” event.
One path around the circle still remains — the “Run flow” command. A flow runs in the background and saves records like a regular user, so its edits raise events in full. That is exactly why there is a limit of “no more than 3 times in 10 minutes”.
The trigger log doesn't help here: it only blocks a repeat of the same rule for the same record, and it doesn't link two different rules.
Mass firing during import
An event is raised for every saved record, not for every button click. Order file imports, website sync, API integrations all create documents one by one, and the rule runs for each. A thousand import lines with an enabled “Send mail” rule without a condition means a thousand emails sent synchronously, right inside the import.
Before first enabling a rule that sends something out (email, SMS, HTTP request), test it on one record: keep the “Active” toggle off, make the condition as narrow as possible (say, one document number), enable the rule, save that document by hand and check the “Operation log”. Only then widen the condition. A sent email can't be recalled.
Several rules on one event
Every rule whose condition matches fires, one by one, by the “Execution order” field, and by name when the order is equal. The first rule can't stop the rest: there is no “stop here” mechanism. So two “Change document data” commands from different rules on one event overwrite each other, and the last one to run wins.
If a run stopped halfway
A rule's commands run one by one, and each successful command is written to the trigger log separately, right after it runs. There is no common “all or nothing” for commands. So if the request broke off in the middle of a rule, this is the state:
- commands that managed to run stay done and have an entry in the trigger log. A sent email, SMS or HTTP request is not recalled;
- commands that weren't reached didn't run and have no entry;
- rules further down the list on this event didn't run either.
You can save the record again. If the condition is met again, the app goes through all commands anew: it skips those that have a log entry (with “Check interval” set to 0, or until the interval has passed) and runs those that weren't reached. Saving again doesn't duplicate what was already sent.
Three exceptions worth knowing:
- if the break happened between running a command and writing it to the log, that command runs again on retry — for example, the email goes out a second time;
- commands marked “Failed!” get no log entry, and saving again will retry them;
- if the condition is built on the “Initial value” option, saving again without changing the field won't meet the condition — the remaining commands won't run until the field changes again.
How to clean up after a wrong rule
First, turn the rule off with the “Active” toggle — otherwise it keeps working while you clean up. What comes next depends on what exactly the rule managed to do.
Posted documents and stock
Unpost a document posted by a rule by hand or with a rule — 0 in the posting field of the “Change document data” command: received goods leave stock, written-off and transferred goods come back. What each document type moves, and when there is no reverse movement, see the section on posting from a rule.
Extra contacts and organizations
The “Create contact” command doesn't create duplicates: it first looks for a card with the same email, or the same name if the command fields have no email. If one is found, no new card appears and the command counts as done. If the email is set but invalid, no card is created at all.
Extra cards are deleted from the contact list with the usual delete button, and documents are not affected:
- deleting moves the card to the “Trash”. Links to documents, price lists and history stay as they were, and the “Restore” button brings the card back with all of it;
- “Delete permanently” in the trash erases the card along with its price lists and their settings, its history and the customer's registration in the store, and products are unlinked from this supplier. Documents stay, but their link to the contact is cleared. Auto-cleanup does the same: cards that stay in the trash longer than 60 days are erased without you;
- an organization created by a rule is the same kind of record in the contact list, it shows in the “Organizations” section and is deleted the same way. Before deleting, check that the rule didn't pick an existing card: if an organization with that name or external already existed, the “Create organization” command doesn't add a new one but puts the existing one in the document and writes the rule's fields to it. The command doesn't change the event's contact card;
- you can't delete your own organization, either to the trash or permanently — the app refuses.
Scenarios
- New rule that emails customers — before enabling it, open the “Rules diagram”: the “No condition — fires on every event” label means the email goes to everyone. Then test it on one document.
- An import of a thousand orders is coming — a rule with no condition will run for every line right inside the import. Turn off rules that send emails, SMS or HTTP requests, or narrow their condition.
- The rule changed the wrong documents — turn it off with the “Active” toggle, find the affected records in the “Operation log” by the rule name and fix the fields or unpost. How to search: if a formula wrote the wrong value.
- Two rules write to one field — the one that ran last by “Execution order” wins. Separate them with conditions or order (several rules on one event).
What to do when a rule misbehaves
| What you see | Why | What to do |
|---|---|---|
| “Failed! Trigger #7 заказ - статус - в обработке Run a command: #8 Send mail” | The command failed. The reason is in a separate log line from the same moment | Find the neighboring line in the “Operation log” (about the log) |
| “Email not sent!” | The mail server refused: the line goes on with the address, subject and error text | Check the mail server settings and the recipient address in the email template |
| “No email provided!” | The email template has an empty recipient: the macro wasn't filled because the contact card has no email | Fill in the email in the contact card or set the recipient in the template explicitly |
| A rule created from “Message templates” fires on every event | There is nothing to build a condition from there: a created there isn't tied to documents or contacts, and the list of condition fields comes from exactly that | Turn the rule off and create it again from the document or contact list (entry points) |
| The rule fires on every document | The condition is empty. A rule is created enabled, so it works before you set the condition | Open the “Rules diagram”: such a rule is labeled “No condition — fires on every event” (about the diagram) |
| The rule is enabled, the condition is right, and still nothing happens | All the rule's commands are turned off by their own checkboxes in the third section | In the “Rules diagram” this shows as “All actions are disabled — the rule does nothing” (about the diagram) |
| An “access denied” picture instead of the window | The user's group has no right to the “Automatic rules” window | Grant the right in group permissions (about access) |
| “Update failed” | An edit made right in the rules grid wasn't saved | Reload the window with “Refresh” in the header menu and try again |
FAQ
How many times did a rule fire?
There is no counter in the interface. Count the “Operation log” lines filtered by the rule number and name.
Why is the “Companies” area empty in the “Rules diagram”?
You can't create rules for this area in the interface, so the “Companies” filter always shows an empty diagram. Document and contact rules are shown in their own areas.
Why did a customer get the email twice after a failure?
The failure happened between sending the email and writing to the trigger log. When the record was saved again, the app didn't know the email had already gone out (about interrupted runs).
Can I edit a rule right on the diagram?
No, the diagram is view-only. The pencil in the corner of a rule block opens its card for editing.
Does the diagram show which email template a command uses?
Yes. The command block shows the email template name or “No mail template selected”, and for a flow, its name or “No flow selected”.
Where to find it and who has access
- Menu
- Account → Operation log
- Rules diagram
- the “Rules diagram” button in the header of the “Automatic rules” window
- Access right
- the “Automatic rules” window; the diagram has no separate right
Related topics
- For the big picture — how automatic rules work.
- If a rule stays silent because it already ran for the record — repeats and “Check interval”.
- If a formula wrote the wrong value to a field — how to fix a formula.
- If you need to find who changed a record and when — operation log.
