Odoo Workflows

1Turn it on

Upgrade the Blipit module to 1.15.0 or later: Apps, Blipit Error Monitoring, Upgrade. There is nothing else to set up. Counting starts with the next button a user presses, and Workflows appears in the app.blipit.io sidebar for projects connected to Odoo. Until the first step arrives, the page says it is waiting for the first workflow from your database.

2What the Workflows page shows

Tiles at the top count the workflows failing, the people affected, the documents waiting and the companies affected. Below them, workflows are grouped by app (Sales, Accounting, Inventory, Point of Sale, Scheduled jobs and so on), each with its success rate and a Failing, Degraded or Healthy status. Filter by app, by company and by the last 24 hours, 7 days or 30 days. Open a workflow to see:

• Attempts, failures, people affected and companies, with the success-rate trend over the window.
• Why it fails: the issues behind the failures, each marked Crash or Blocked, linked to the issue page.
• Documents waiting: every order, invoice or delivery a failed step touched, each linked straight back to the record in your Odoo.
• The issue page shows the same link from the other side: the workflows an error broke and the records it touched. The Overview shows your three worst workflows.

3Which steps count

Blipit counts the buttons that move a document forward: Odoo's own, such as Confirm quotation, Create invoice, Post invoice, Register payment, Credit note, Validate delivery, Confirm purchase order and Close POS session, and the action_ and button_ methods of your custom modules, which appear under their app with a name made from the method (action_approve_order becomes Approve order). Every scheduled job run counts too, including Run manually, and so do server actions started from the Action menu. Opening views, printing and other reading calls are not counted, so the list stays short.

4Blocked, crashed and timed out

Each attempt ends one of four ways. Success: the step finished. Blocked: Odoo stopped the user with a message they can act on (a UserError, ValidationError or AccessError, such as a missing account or a missing route). Crashed: an unexpected error. Timeout: Odoo stopped a scheduled job for running too long. Blocked steps are counted in full for the success rate, and 1 in 20 is also kept as a warning event so you can read the cause; blocked steps never page anyone. Crashes and timeouts arrive as error events like any other.

5Counted every minute

Each Odoo worker adds up its attempts in memory and sends them to Blipit once a minute in one small request, and sends nothing while idle. Deciding whether a call is a workflow is a simple lookup with no database query, so pages are not slowed down. The counts are not billed as events; only errors and the blocked samples count toward your plan's events.

6The banner on the record

When a step fails on a record, people who open that order, invoice or delivery in Odoo see a red banner saying which step failed, when and why. It clears when the step next succeeds on that record. Only internal users see it. The banner needs Solo or a higher plan and is on by default; turn it off in Odoo under Settings, Blipit, Workflows. In the same place you can turn on a one-line chatter note on the record when a step fails. The note is off by default because it writes to your records.

7Alerts

The Alerts page has a Workflow alerts section with two rules, both on from the start. Failing for many people fires when 3 or more people hit a crash on the same workflow within 10 minutes. Scheduled job failing fires when a scheduled job fails 2 runs in a row or times out. You can change the threshold and the window, or switch a rule off. Workflow alerts go to the same people and channels as your other alerts (email rules, Slack, Microsoft Teams and webhooks, or the owners when there are none), respect snoozes and the hourly alert budget, send one notice per workflow, and send an all-clear once the problem has been gone for 15 minutes. Blocked steps never raise an alert.

8Plans

• Every plan: failures by workflow, the people affected, the documents waiting with their Odoo links, the causes, and the Failing for many people alert.
• Solo and up: success rates, attempts and the trend, the Scheduled job failing alert, and the banner on the record in Odoo.
• History: 7 days on Free, 30 days on paid plans.
• Attempts are counted on every plan, so success rates appear for your recent history as soon as you upgrade.

9Privacy

Successful steps are sent as counts only: the workflow, the company and how many. A failed step also sends the record ids of the documents it touched (up to 20), the Odoo user id and the company id, all as plain numbers. Workflow data never carries amounts, names or messages. The message Odoo showed a blocked user stays inside your own Odoo database, where the banner reads it. The 1 in 20 blocked samples are error events, and their message has numbers and quoted values removed before it leaves Odoo.

Good to know

• Works with Odoo on your own servers and on Odoo.sh. Odoo Online does not allow third-party modules.
• When Odoo restarts a worker, for example after it reaches limit_request, up to a minute of that worker's counts can be lost. Success rates tolerate this.
• When Odoo retries a step after a database conflict, only the final outcome counts.
• Errors from older module versions still show their workflow on the issue page when the request names the button, but success rates and documents waiting need 1.15.0.
• Record links open your Odoo at the address the module reported when it connected, as /odoo/<model>/<id>.
• Failed-step records follow your plan's workflow history; a record whose step later succeeded is deleted after 7 days.