---
title: "Known issues and workarounds"
description: "A short list of the things in Wave that don't behave the way you'd expect, plus the workaround. We update this page as we find and fix issues."
group: "troubleshooting"
lane: "how-to"
status: "published"
publishedAt: 2026-05-15
sidebarOrder: 10
tags: ["troubleshooting", "known-issues"]
relatedSlugs:
  - "estimates/add-room"
  - "estimates/edit-line-item-via-chat"
  - "estimates/upload-photos"
  - "estimates/reorder"
  - "estimates/chat-questionnaire"
  - "account/contact-support"
sidebarLabel: "Known issues"
---

A short, honest list of things in Wave that don't yet behave the way you'd expect. Each one has a workaround and an open ticket on our side.

## Adding a room via the UI doesn't work

The **+** button next to "Show Codes" in the workspace looks like it should add a room. It doesn't reliably do that — it's a broken target.

**Workaround:** Add rooms through chat. *"I want to add the laundry room"* / *"Can we add a coat closet to this estimate?"* See [Add a room mid-estimate](/docs/estimates/add-room).

## Chat treats "General" as a candidate new-room name (dev-acknowledged)

When you issue a chat command targeting a line item in the **General** section — *"Delete the dumpster line from the General section"* — Wave can misinterpret "General" as a room name you're trying to add. The actual response in the wild has been:

> *"'general' doesn't exist. Do you want to add it in hall bathroom or hallway?"*

This is a known bug acknowledged by the dev team. Until it's fixed:

**Workaround:**

1. **Do General-section edits manually via the right pane.** Open the line-item kebab and use Edit / Modify ▸ / Delete Item directly. See [Edit a line item manually](/docs/estimates/edit-line-item-manually) and [Delete a line item](/docs/estimates/delete-line-item).
2. If you still want to use chat, try omitting the section name entirely — *"Delete the dumpster line"* — Wave will try to disambiguate from context.

Room-scoped sections (Hall Bathroom, Hallway, etc.) work fine — this is specific to General.

## Wave occasionally asks for info you already gave

Sometimes during the per-room interview, Wave will circle back and ask for a detail you've already answered. We've squashed most of these but they still pop up occasionally.

**Workaround:** Just answer the question again. If you want to flag it, *"I already answered that — \[your answer\]"* is fine.

**One thing to watch for:** keep your answers **consistent**. If you say yes to a question and then say no to the same question later, Wave can get confused about which is current and the estimate may go sideways. Pick the right answer and stick with it.

If this happens repeatedly on the same estimate or on a fresh estimate, [contact us](/docs/account/contact-support) — we want to see the cases that still slip through.

## Wave says the estimate is done, but the right pane stays empty (high priority — please report)

Wave normally signals completion with *"Your estimate is ready! 🎉"* and the full set of line items appears in the right pane. Every once in a while Wave gets stuck on missing info it didn't know to ask for, and it'll say something close but not quite the canonical message — *"Your estimate is complete"* or *"I have all the details"* — without the 🎉 emoji and without the line items actually appearing in the right pane.

This bug is 99% squashed but it can still occur.

**Workaround:**

1. **Recreate the estimate.** The current one is stuck — there's nothing to recover.
2. **Before starting over, gather your answers.** Write down or memorize the FNOL fields, room measurements, surfaces, demo scope — anything you already told Wave. Front-load that into your first message and the first few answers so Wave has more context up front.
3. **Restart.** Open a new estimate and walk through the interview again.

> **We care about this one a lot.** If it happens to you, please [contact support](/docs/account/contact-support) right away. Include the estimate ID, the customer name, and roughly where in the interview Wave got stuck. The more reports we get, the closer we get to the last 1%.

## Room grand totals occasionally don't reconcile

Every now and then a room's displayed grand total doesn't equal the sum of its line items — e.g., a bathroom shows ten line items that should add to $1,427 but the room total reads $1,200. The line items are correct; the displayed total is the one that's stale.

**Workaround:** Trigger a reprice.

1. Add any new line item to the affected room — even a placeholder.
2. Wave reprices the room total when the line item appears.
3. Delete the placeholder line item.
4. Wave reprices the room total again — this time to the correct amount.

The room total settles to the accurate number on that second reprice. The Grand Total at the bottom of the estimate is recomputed in the same pass, so it'll also be correct.

We're tracking the underlying reconciliation bug. Until it's fixed, the add-and-delete reprice is reliable.

## Reorder doesn't always persist across page reloads

You can [drag and drop line items and rooms to reorder them](/docs/estimates/reorder). The new order is reflected in the workspace immediately. But occasionally, if you leave the estimate and come back to it later, the order has reverted to the original — Wave wasn't able to persist the reorder state.

**Workaround:** **Reorder and export in the same session.** The PDF export captures the order *currently displayed* in the right pane, so as long as you don't reload between reordering and clicking Export, the PDF lands in the correct order. The PDF is the artifact the customer / adjuster actually sees, so the persistence bug doesn't reach them.

If you do reload and the order reverts, drag the rows back into place and export immediately. We're working on the underlying save issue.

## Autofill suggestions don't always populate the form

In the **Add Line Item** modal, the autofill catalog suggests pre-formatted items as you type. Clicking one of those suggestions should fill the form with the catalog item's defaults. It doesn't always do that.

**Workaround:** Type the full description manually. The line item gets created normally; you just don't get the catalog auto-fill.

## Photos can't be reordered or re-captioned

After uploading photos to **Documentation Photos**, you can't:

- Reorder photos within a room (captions are derived from upload order)
- Change an individual photo's caption (captions are auto-generated from the room tag)

**Workaround:** Use the Documentation Photos kebab → **Delete** to remove the photo (see [Download photos](/docs/estimates/download-photos) for the same selection-based flow), then re-upload it. The upload order resets, which lets you indirectly control the caption order. Full per-photo controls (reorder, custom captions) are on the roadmap.

## Breadcrumb kebab a11y label is stale

The kebab at the top-right of the estimate opens with four actions: **Lock, Export, Duplicate, Delete**. The screen-reader / a11y label still says *"Open estimate actions menu (Lock, Export, Duplicate)"* — only listing three. The visible menu is correct; the a11y string is outdated.

If you're using a screen reader and the label sounds short, trust the visible menu. We'll update the label.

## Cancel isn't in the breadcrumb kebab

Cancel is **not** one of the four kebab actions. To set an estimate to **Canceled**, change the status from the **status badge** instead — see [Change an estimate's status](/docs/estimates/change-status).

The kebab's red **Delete** is a *permanent* destructive action, not the same as Cancel.

## Adding a room can slightly reprice other rooms

When you [add a new room](/docs/estimates/add-room), per-room totals on the existing rooms can shift slightly — usually downward. This is **expected behavior, not a bug**.

Some line items are sized against the whole estimate (shared equipment that now serves more rooms, for example), so adding scope can lower the per-room allocation even as the Grand Total goes up. Focus on the Grand Total / Overall Grand Total in the [Estimate Summary](/docs/estimates/export-pdf) — that's the bottom-line number.

## "General" in the app shows up as "General Charges" on the PDF

In the right pane and in chat commands, the cross-cutting section is called **General**. On the exported PDF, the same section header reads **"General Charges."** Same content, different label.

If you're cross-referencing the app to a generated PDF, this is the only section name that changes.

## Cancelled (British) vs. Canceled (American) — app-wide inconsistency

Wave uses British **"Cancelled"** in most places but American **"Canceled"** on the top-nav filter tab. The rule:

| Where | Spelling |
| --- | --- |
| Status pill in the estimate | **Cancelled** (British) |
| Status dropdown option | **Cancelled** (British) |
| Breadcrumb suffix | **Cancelled** (British) |
| Top-nav filter tab | **Canceled** (American) |
| URL parameter value | `cancelled` (British) |

If you're searching docs or scripting against URLs, use the British spelling everywhere except the literal top-nav tab text. See [Find and filter estimates](/docs/reference/filters-and-urls).

## When you hit something not on this list

[Contact support](/docs/account/contact-support). We use the messages we get through in-app support to decide what to fix and what to document, so reporting an issue actually moves the needle.

## Related

- [Add a room mid-estimate](/docs/estimates/add-room)
- [Edit a line item via chat](/docs/estimates/edit-line-item-via-chat)
- [Upload and tag photos](/docs/estimates/upload-photos)
- [Contact support](/docs/account/contact-support)