Duaer

Build

Replay a generated workflow, then publish it in Duaer

Before a workflow generated from a process is published, Duaer replays the saved version over the cases of the past 7, 14 or 30 days: whom it would have sent cards to, and whether they were right. A fit of 60% lets it publish; below that, an owner or admin can publish it with a note, which is kept in the audit log. An Execute action must also come after an approval.

What a replay does

A replay runs the version you saved, your own edits included. For each past day Duaer rebuilds the cases as they were that day, runs the workflow at that day’s scheduled time and sees whom it would have sent cards to; for Coordinate it takes the next step each case really took as the choice.

A replay writes no data, saves no execution and calls no outside system: nodes that send cards, write back, call HTTP, send mail or use AI only pass their input on. An organization runs one replay at a time.

Run a replay

  1. Open the workflow and select the Generated from process badge in the header.
  2. Under Replay, choose Days: 7, 14 or 30, and select Run replay. Owners and admins can run it; members can view it.
  3. The result appears after a few seconds to a few minutes. The replay ends at the last step in the data, leaving out times in the future.

How to read the fit

  • Watch and Execute: the fit combines precision and recall (F1). Precision is the share of carded cases that really were overdue; recall is the share of really overdue cases that got a card. Below, Flagged, not overdue and Overdue, not flagged list the case ids.
  • Coordinate: fit = 0.7 × right next step + 0.3 × right owner. Right next step: the step the case really took next was an option and the run reached its branch. Right owner: the card went to the person who really did the next step. Coverage is shown, not scored: a case decided before the daily check never got a card. Below, Next step not reached and Decided without a card list the cases.
  • History keeps every replay and every publish note; those of earlier versions are marked older version.

For example, a laboratory source replayed over 30 days: the Watch workflow fits 95% (precision 91%, recall 100%); a Coordinate workflow on manufacturing orders fits 78% (right next step 100%, right owner 27%, coverage 76%). A low right-owner share means the owner column holds the last person who touched the case, not necessarily who does the next step.

Publishing rules

  • When the newest replay of this version fits 60% or more, it shows Ready to publish; publish as usual.
  • Every save is a new version, and a new version needs its own replay.
  • Without a replay, or below 60%, Publish opens Replay this version first with the reason. An owner or admin can write a note and select Publish with note; the note counts for that version only and is kept in the audit log as Published generated workflow without replay.
  • Execute workflows have one more rule: every enabled node that may act outside Duaer needs a Wait that a person resumes (the approval card) before it. Otherwise Publish opens Approve before acting and names those nodes, and no note overrides this.

Questions

Does a replay really send cards or call my systems?

No. A replay writes no data, saves no execution, calls no outside system and does not change the workflow.

I changed one limit. Why can’t I publish now?

Every save is a new version, and the check looks at the version being published. Run a replay of the new version; with a fit of 60% it can be published.

What if the fit stays below 60%?

Look at the case lists first: too many cards (raise the limit), missed cases (lower it) or the wrong owner (check the owner email column). If it has to go live anyway, an owner or admin can publish it with a note.

Can a note override the approval rule of an Execute workflow?

No. Acting outside Duaer always needs a person’s approval first. Move the action back after the approval Wait, or disable it.

In this section

Process

Watch, Coordinate and Execute: the workflows Duaer generates from a process

From one process source Duaer can generate three workflows. Watch reminds an owner when a case waits too long. Coordinate asks the owner which way a case goes where cases branch, and writes the choice back. Execute asks the owner to approve starting the next step and then reaches a suggested action that a person reviews and enables.

Process

See the process in your data and generate workflows in Duaer

Duaer reads the steps every case went through from the tables, databases or Feishu apps you already have: where cases wait too long, where they branch and who did each step. From that it generates three kinds of workflow, Watch, Coordinate and Execute, and replays each over past days before you publish it.

Manage

Save and publish a workflow in Duaer

In Duaer, edits stay a draft until you publish. Schedules, webhooks, and production runs use the published version.