Fixing Workflow Errors with AI
Description
Section titled “Description”When a workflow step fails or logs a warning, the AI fix assistant reads that error, works out what caused it, and — when the cause is a misconfiguration of the step itself — proposes a corrected configuration and applies it once you approve. It goes beyond explaining the error: it can make the change for you.
It is part of PlaidCloud’s Weave AI and opens in the Weave dock, already pointed at the step that failed, from the project’s Log viewer, the workflow editor and the project’s Weave tab. When a scheduled run fails, Weave can have the fix waiting for you; see A Fix Waiting After a Failed Run.
Opening the Fix Assistant
Section titled “Opening the Fix Assistant”From the project’s Log tab:
- Open the project and click the Log tab.
- In the log list, select the entry for the step that failed. Its full message — including any stack trace — opens in the panel on the right under Log Message.
- Click Fix under the message. An error or warning from a step offers Fix; other entries offer Ask Weave. ⋯ beside it has Explain and the other Weave actions.
The dock opens already pointed at the workflow and step the selected log entry came from, so it starts diagnosing straight away — you don’t have to tell it which step failed. You can read the raw error under Log Message while the assistant answers in the dock. For a few common errors its first reply is an explanation instead — see Common Errors.
From the Workflow Editor
Section titled “From the Workflow Editor”Select a step with a red dot on the canvas. In the Inspector, the Last Run Error card has Fix beside its heading when the fix assistant is on, and Ask Weave otherwise. See When a Step Fails.
From a Right-Click
Section titled “From a Right-Click”Right-click the step on the canvas or in the step list, or the error line in the log, and choose Fix in the Weave section of the menu. Fix is offered when the step’s last run failed or a finding offers one, and never on a warning line. The Weave dock opens on that step. In Monitor or the Log viewer, Fix on a row does the same.
From the Weave Tab
Section titled “From the Weave Tab”In the project’s Weave tab, click Fix on the card of a problem Weave found. The assistant opens in a window of its own, already pointed at the step the problem is about, and starts from the problem as Weave reports it now. See Fix a Finding with the AI Assistant for which findings offer Fix.
How It Works
Section titled “How It Works”- Diagnoses — it reads the failing step’s configuration and the tables and columns it touches, and checks its claims against your data rather than guessing from the error text alone.
- Proposes — if it finds a genuine misconfiguration, it shows the change on a card: Why it failed in one sentence, then a box for each setting that changes, named where it can be as it is on the step’s form, with the current value in red and the new value in green. Only what changes is listed — for a column list, just the columns that change. Nothing is saved at this point.
- You approve — select Approve N changes on the card, or Not now to leave the step as it is. Replying in your own words works too. The buttons become available once the assistant has finished its reply, and your approval always comes in a message after the proposal.
- Applies — once you approve, it writes the change to the step, through the same path the step editor uses. What gets saved is the change on the card, and one approval saves it once. Just before saving, it keeps a copy of the step’s settings as they are, so you can undo the fix — see Undo a Fix.
- Re-runs and confirms — in the browser, the same approval covers the re-run: Weave re-runs the fixed step with ERP posting off and tells you whether it succeeded, finished with a warning, or failed again, for example Fixed and re-run: Allocate by Driver succeeded in 4 min, 46,812 rows, within its usual range. If it couldn’t confirm, it says why and never says the step is fixed. In the mobile app, a second card asks whether to re-run the step. If the step hasn’t finished within two minutes, Weave says so, and the result shows in the workflow and the Log tab.
The assistant doesn’t offer a re-run for a step that posts to an ERP system or runs another workflow — re-run it from its workflow, where you choose the ERP posting mode — or when the chat isn’t tied to a workflow, or when your role can’t run workflows. If the workflow is already running, nothing runs and the assistant offers to try again.
Each proposal, your approval or rejection, and the change itself are recorded in the project’s Weave activity history, with exactly what the change replaced and wrote. Your approval is recorded before the change is made. If it can’t be recorded, nothing is saved and the card says so, and you can approve it again later.
A Fix Waiting After a Failed Run
Section titled “A Fix Waiting After a Failed Run”When a workflow run started by a schedule or a sensor fails, Weave looks at the failure straight away and, when it can, prepares the fix before anyone opens the log. For a run you started by hand, it prepares a fix when the cause is a source column that was renamed.
The fix waits as a card titled for the failure, such as Month-End Close failed at Allocate by Driver. It says why the run failed, what changes, and what it re-runs: Then: re-run Month-End Close from Allocate by Driver, then Margin Report. ERP posting is off for these runs. You find it:
- in the failed run’s row in Monitor → Findings, which opens to show the card;
- on the log entry and on the step’s mark on the canvas;
- in the dock, as a Waiting for you row.
The card’s owner is told in PlaidCloud, Month-End Close failed. Weave has a fix for you to review., and on their phone if they use the mobile app. Click Apply and re-run to save the fix and re-run from the failed step. Weave then says whether the run succeeded.
- Anyone whose role can edit the failed step, and the card’s owner, can approve it, on the web.
- Weave prepares one card for each cause, and doesn’t look again at the same failure on an unchanged step once it found no fix or the card was declined.
- A step that posts to an ERP or writes outside PlaidCloud gets no card.
Fix Several Steps at Once
Section titled “Fix Several Steps at Once”When the same problem affects several steps, such as a renamed column used in six mappings, Weave proposes all the changes on one card with a numbered section for each, what it will re-run, and anything it couldn’t include, such as a step your role can’t edit. One Approve 6 changes applies them all, then Weave re-runs each fixed step once, with ERP posting off, and says whether the problem is gone. If a step changed after you approved, Weave doesn’t apply it and stops, and says how many were applied. One Undo puts every fixed step back. If Weave prepared the card while you were away, it waits in that conversation in the dock, as a Waiting for you row you open to approve; see Cards Waiting for You.
Undo a Fix
Section titled “Undo a Fix”A fix’s card says when the fix can be undone: Weave keeps a copy of the step’s current settings, so you can undo this for a limited time, unless the step is changed again first. A card without that line can’t be undone. If Weave can’t keep the copy, it saves nothing and says so, and you can ask it again.
Once the fix is saved, the card shows Undo. The fix’s entry in the project’s Weave activity history has the same button, so you can undo a fix after its chat is closed. Anyone whose role can change steps in the project can undo a fix, not only the person who approved it.
Undo opens a window that shows what undoing puts back: each setting the fix changed, as it is Now and as it will be After Undo. Then choose:
- Undo — put the step’s settings back as they were just before the fix.
- Undo & Run — put them back, then run the step. It’s offered when your role can run workflows, the step is still in the workflow the fix was made in (or, failing that, in only one workflow) and you can open that workflow, and the step doesn’t post to an ERP system or run another workflow. The run itself can’t be undone.
- Cancel — leave the step as it is.
Undoing changes the step’s settings only. Data that runs of the step have already written stays as it is: re-run the step to rebuild it.
Weave won’t undo a fix, and changes nothing, when:
- The step has changed since the fix. Undoing would put back settings that are out of date, so the window shows the step as it is Now beside its settings Before Weave’s Change, and you can change it yourself.
- The step already has the settings it had before the fix.
- The copy is no longer kept. Copies are kept for a limited time.
- Your role can’t change the step, or the project is locked.
- Weave couldn’t record the undo. Try again later.
An undo is recorded in the activity history as a change of its own, such as Done as approved: undo Weave’s change to a step’s settings.
Common Errors
Section titled “Common Errors”When a step fails with one of these common errors, the first reply is an explanation PlaidCloud already has for that kind of error, so it appears straight away.
On any type of step:
- an expression that uses a column that isn’t in the table the step reads
- a column mapping whose source column isn’t in the table the step reads
- a step that stopped before writing anything because its source tables don’t match its settings: a column it uses or a join key that a table doesn’t have, a join key the step doesn’t list, or a source table that hasn’t been built
- a setting the step needs that was left empty, such as the connection it uses or the table it reads
- a workflow the step runs that failed — the cause is most likely in one of that workflow’s steps, so check that workflow’s log
- a table the step names that can’t be found
- a Snowflake or Databricks warehouse that blocks PlaidCloud’s address, rejects its sign-in, has used up its quota, can’t be found or used, or is missing a privilege PlaidCloud’s role needs
On a SQL Extract step:
- SQL that can’t be read as written, such as a misspelled keyword or a bracket that isn’t closed
- a function the database doesn’t recognize
- a table that doesn’t exist
- a function given a type of value it can’t work with, such as adding up a text column (on Databend)
- a value that can’t be converted to the type the SQL asked for, such as text where a number or a date was expected (on Databend)
On a Table Extract step, with fixes that point to the step’s own tabs and fields rather than to SQL:
- a source table that doesn’t exist yet, or no longer does (on Databend)
- an expression that uses a function the database doesn’t recognize (on Databend)
- a function given a type of value it can’t work with, such as adding up a text column in an expression or with Summarize (on Databend)
- a step with no output columns, such as one whose columns were all removed
The explanation says what usually causes the error, which words in the error message to look at, and how to fix it. It is general: it doesn’t check your step or change anything. To have the assistant look at the step itself, reply. From then on it works as described in How It Works, with the explanation as part of the conversation.
Any other error goes straight to the assistant’s own diagnosis. That includes the database errors listed above when they come from any other type of step.
What It Can Fix
Section titled “What It Can Fix”The assistant repairs the configuration of the one step the error came from — for example a mistyped column or function name, an invalid expression, a wrong data type or cast, or malformed SQL. It changes the least that fixes the error: one failure, one targeted change, with the rest of the configuration left as it was.
An expression that fails — in a column, a filter, or a having clause — is handed to the same expression specialist that sits beside the Expression Editor, with the error and the source table’s columns. The corrected expression it returns is checked before it is proposed, and the proposal is still a change to that one field of the step, approved the same way as any other.
What It Won’t Do
Section titled “What It Won’t Do”Its only lever is that step’s configuration, and it is upfront when the problem lies elsewhere rather than bending an edit to look like a solution.
- It edits one step’s configuration and nothing else — it won’t create, delete, or reorder steps, create tables, edit a different step, or change your data.
- Many failures aren’t configuration problems: missing or malformed source data, an upstream step that failed first, a transient or infrastructure error, a permissions issue, broken Python in a UDF or a user-code step, a missing file in a document account, or a resource or timeout limit. For these it explains what it found and points you to where the real fix lives.
- Warnings are often benign and need no change — it will say so plainly rather than invent an edit.
- When it isn’t certain a change will work, it says so and names what it’s unsure about instead of presenting a guess as a certainty.
- The diagnosis is grounded in your live step configuration and table metadata, so it reflects the project as it is now — not a cached or assumed shape.
- After a fix is applied, say yes when the assistant offers to re-run the step, or re-run it yourself, to confirm the error is resolved.
- If the assistant says the cause is outside the step’s configuration (bad data, an upstream failure, a permissions problem), that is the answer — fix it where it actually lives rather than asking the assistant to edit the step anyway.