Weave Tab — Read and Act on Weave's Findings

Description

Every project has a Weave tab that lists everything Weave has noticed about the project’s steps and workflows — the problems it found and the things it could not check — in Weave’s own words. From the tab you can read each finding in full, mark findings as read, and open the step or workflow a finding is about.

For what Weave checks and what its answers mean, see What Weave Checks.

Open the Weave Tab

There are three ways in:

1. Open the project and select the Weave tab, next to Log.
2. In the project’s Workflows tab, click a workflow’s mark in the Weave column. The Weave tab opens showing only the findings about that workflow.
3. Follow a link to the tab. While the Weave tab is in front, the browser’s address bar holds a link to it, which you can bookmark or share with someone who can open the project.

The tab appears for anyone whose role lets them see the project’s steps and workflows; for anyone else, a link to it opens the project instead. Weave reads the whole project when the tab opens, so a large project can take a moment to list.

What the Tab Shows

The two lines at the top are Weave’s summary of the whole project: how many of its steps and workflows Weave checked, what it found, and what it has no rule for. They carry their own counts, so the list below is never mistaken for a verdict on the whole project.

Each row of the list is one finding:

Column	What it shows
Status	Red for a problem, amber for something worth a look, a question mark where Weave could not check.
Finding	Weave’s sentence about the step or workflow.
About	Whether the finding is about a Step or a Workflow.
Workflow	For a step, the workflow it belongs to, or how many it belongs to. For a finding about a step’s run, the workflow whose run it was. A workflow your role doesn’t show you appears as A workflow you can’t see.
Why Unchecked	For something Weave could not check, the reason.
Read	Unread until you mark the finding read.

Problems are listed first and the things Weave could not check after them, in the order Weave reports them. The columns can’t be sorted, so that order holds.

Select a finding to read it in full beneath the list, along with the rule that produced it, why Weave could not check it where that applies, and — for a finding about a step’s run — which workflow’s run it was.

The reasons a finding can give in Why Unchecked are:

• Not fully set up — the step or workflow is saved but not finished, such as an allocation with an empty column mapping or a workflow with no steps yet.
• Needs run history — Weave needs runs it has no record of: the workflow hasn’t run in the last 30 days, hasn’t run often enough to compare against, or its runs carry no empty-value counts.
• Needs more context — Weave lacks something it needs, such as a variable that is set differently in each workflow the step belongs to, or run history it could not read.
• Configuration it can’t read — the step’s configuration is in a shape this check does not read.
• The check failed — the rule itself could not run.

Show One Workflow’s Findings

Clicking a workflow’s mark in the Workflows tab opens the Weave tab on that workflow’s findings only, with a line above the list naming the workflow. The tab reads Weave’s findings again when you click a mark, so the list matches the mark you clicked even if a run has changed it since you last looked. Click Show All to see the whole project again.

A workflow wearing a tick has no findings, so its view says No Weave rule reported this workflow, and beneath it what Weave has no rule for across the project, just as the tick’s tooltip does. A tick means no rule reported the workflow, not that every part of it was checked.

Mark Findings as Read

• Select one or more findings and click Mark Read.
• Click Mark All Read to mark every finding listed. When the list shows one workflow’s findings, only those are marked.

Opening the tab marks nothing read, and neither does being told about a finding when a run ends. Read state is yours alone.

A finding you have read can come back as unread. Weave treats a finding that says something new as a new finding — a run finding describes the run it came from, and a configuration problem that changes is a different problem — so it appears unread until you read it again. If a finding changed between the list loading and you marking it, the tab reloads the list.

Marking a finding read also stops it being mentioned in the message you get when a run ends. See Being Told When a Run Ends.

Go to the Step or Workflow

Select a finding and click Go To, or double-click the finding.

• A workflow opens on its canvas if it is an Advanced workflow, or on its Steps grid otherwise.
• A step opens inside its workflow with the step selected. When the step belongs to more than one workflow, Go To lists them by name and you choose which to open — Weave never picks one for you.
• A step’s run finding opens the workflow whose run it was, since that is the run the finding is about.
• A step that belongs to no workflow you can see opens on its own.

When Weave Is Unavailable

If Weave’s findings can’t be read, the tab says Weave is unavailable instead of showing an empty list, because an empty list would look like a project with nothing wrong. Click Try Again, or Refresh on the toolbar.

Note

When Weave has nothing to report, the tab shows Weave’s own summary of the project rather than a message saying all is well. That summary says how much of the project was checked, so it can’t be read as covering everything.

Click What Weave Checks on the toolbar to open What Weave Checks.