Matched assets are slow or missing

3 min readLast updated: Sep 23, 2026

On the Assets & Team step of the proposal wizard, Propivix lists the assets from your library that best fit the RFP, and marks which requirements each one supports. This article covers what to do when that list is slow, missing, or shows less than you expect.

Why the first load is slow

Propivix starts matching assets as soon as you pick the RFP in the wizard. It reads the RFP's requirements against the assets in your library, which uses AI and can take several seconds. While it runs, the step shows "Loading matched assets...".

Later loads for the same RFP are usually much faster. Propivix keeps the results and reuses them until something they depend on changes:

  • the RFP's requirements, for example after a re-analysis
  • the assets in your library, when one is added, edited or removed
  • the business line you choose on the Strategy step, which changes which assets are considered first

So the first visit after one of those changes is slow again. That is expected.

When matching does not finish

The wizard waits up to 45 seconds for matching. If it does not finish in time, or fails along the way, the step shows:

"Asset matching did not finish. You can continue and select assets manually."

The step then shows no asset list, and no assets are selected for you. You have two choices:

  • Continue through the wizard without matched assets. The rest of the wizard still works.
  • Leave the wizard and open it again for this RFP later, to run matching again.

Sometimes matching fails in a way that does not show this message. The step then lists assets from the rest of your library instead of matched ones. Those cards show AI relevance only, with no evidence chips.

If matching fails every time for the same RFP, contact support with the RFP page address and the time you tried.

Why evidence chips are missing

Each card normally leads with an evidence chip, such as "Evidence for 4 of 30 requirements", and carries an "AI relevance" chip as a secondary picking aid. A card can show AI relevance only, for three reasons:

  • The RFP has no extracted requirements, so there is nothing to measure evidence against. Check the RFP's compliance matrix. If it is empty, see Re-analyzing an RFP.
  • The evidence check could not run this time. The rest of the step still works. Open the wizard again later to try again.
  • The asset was listed from the rest of your library, beyond the matching results.

A card reading "No requirement evidence yet" is different. The check did run, and this asset is not among the best matches for any requirement. That is a statement about the asset's wording, not an error.

AI relevance is not coverage. A high AI relevance does not mean the asset supports any particular requirement. For what each chip means and how cards are sorted, see Requirement evidence on assets.

Was this article helpful?

Still have questions?

Our support team is happy to help.

Contact Support
A clearer path to your next win

Ready to Apply This in Your Workflow?

Book a demo and we will walk you through setup with your team.