Repair
A repair fixes a scripted workflow’s test script when it breaks. This happens when your product changes in a way the existing script can’t handle (a renamed element, a changed flow, a new step).Auto-repair
Lark can repair workflows on its own. When a scripted workflow’s execution fails and the workflow entersneeds_repair status, Lark kicks off a repair if auto-repair is enabled for your account.
Auto-repair is an account-level setting. You can enable or disable it in the dashboard.
Manual repair
Trigger a repair from the dashboard or the API: Navigate to the workflow in the dashboard and click Repair. Or trigger a repair through the API:Regeneration
You can also regenerate a scripted workflow if you materially change the purpose of the test. Navigate to the workflow in the dashboard and click Regenerate under the⋮ menu.
Repair vs. regeneration
| Repair | Regeneration | |
|---|---|---|
| Does what | Patches the existing script | Rebuilds the script from scratch |
| Use when | A small change broke the test | The test needs a full rewrite |
| Can be automatic | Yes (auto-repair) | No, manual only |
| Preserves existing logic | Yes, changes only what broke | No, starts fresh |