A deal is not on the board

Before anything else, check what the board is showing#

The pipeline is a view over opportunities, and a view has a shape. A search term still in the box, a stage filter left from yesterday, or a date range narrower than the deal's age will all hide a record that exists and is perfectly healthy. Clearing the view is thirty seconds and settles most of these.

The Data grid is the useful second opinion. It reads the same records through a different surface, so a deal that appears there and not on the board is being hidden by the board, and a deal that appears in neither is genuinely not in this workspace.

The four causes, in the order worth checking them#

1. A filter or a search term. Including a % or an _ typed into a search box, which is matched as an ordinary character rather than as a wildcard — so searching for 50% finds the text 50% and not everything.
2. The stage. Closed stages are usually out of the default view. A deal marked won or lost last week has not gone anywhere; it is sitting in a column you are not looking at.
3. Ownership or linkage. A deal opened against a person who was later merged, or against a person with no company linked, can be filed where you are not looking rather than missing. customer_360 on the person shows what is attached to them.
4. The workspace. Deals belong to exactly one workspace. An Owner session and a customer session see different boards through the same screen, and a deal created in one is invisible in the other by design.

What Connect completed#

• It stored the opportunity when it was created, in the workspace whose session created it, with the stage and any value it was given.
• It kept the deal on the person and on the timeline. Even when the board is not showing it, the relationship record still holds it.
• It answered the query the board asked. Counting, filtering, searching and paging happen in the database, so what you see is a faithful answer to the filter you set — including an empty one.

What Connect did not complete#

• It did not delete anything. There is no automatic removal of deals from the pipeline; a missing card is a hidden card or a card in another workspace.
• It did not move the deal for you. If the stage is unexpected, somebody or something moved it, and the decision record says who.
• It did not surface a cross-workspace record, and never will. That is the isolation boundary rather than a filter you can widen.

What you can do#

1. Clear every filter and the search box, and set the stage filter to show closed stages.

   Result Most missing deals appear at this step, usually in won or lost.

2. Open the person the deal belongs to and read their record.

   Result customer_360 shows the deals attached to that person whatever the board is filtered to.

3. Check the workspace name in the session before you go further.

   Result You find out you are on the other audience before you spend twenty minutes on a fault that is not one.

4. If the person was recently merged, look at the surviving record rather than the one you remember.

   Result A merge carries deals across; the deal is on the survivor, under a name you may not have searched for.

What an administrator can do, and when to escalate#

An administrator can confirm the member's permissions and check the decision record for the deal, which answers who moved it, who merged the person it hung from, and when. On a workspace with a long pipeline it is also worth confirming which stages the default view excludes, because that default is the single commonest reason a healthy deal looks lost.

Escalate only when the deal is absent from the board, absent from the Data grid, absent from the person's record, and you are certain of the workspace. That combination is worth reporting with the deal's name, roughly when it was created, and the person it was opened against — and without pasting the customer's contact details into the report.

Questions#

Related#

• The pipeline board
• Customer 360
• Merging two records
• Website enquiries
• The deal would not move stage
• Data that should be here is not