The run stays queued
Queued means the request was accepted and is waiting to start. Do not repeatedly select Run Comps or Refresh Comps. The control is disabled while the request is already queued.
If the state does not progress after a reasonable processing period, reload the property and check the run selector. If it remains pending, contact support with the property and run time.
ReiSearch says a run is already in progress
A duplicate-order message means the service already has a comp-generation request in progress for the property. Wait for that run to complete or stop it when the Stop action is available.
The account has insufficient credits
Comp generation can require account credits. When the service returns an insufficient-credit or missing-wallet state, ReiSearch opens the token-shortage flow. Resolve the account requirement before resubmitting the run.
The run failed
A failed state means processing did not complete successfully. Check:
- The subject property has a valid address and location.
- The subject contains the core property characteristics needed for comparison.
- Your account has permission and sufficient credits.
- No duplicate run is already processing.
Try again once. If the service continues to fail, contact support with the property, comp type, and approximate run time.
No comps are available
No comps available means the active run and comp type do not contain displayable results. Check that you selected the intended run snapshot and comp type. A different strategy tab has a separate result set.
Results exist but none match
No comps match your current search or filters means the run contains results, but the current controls exclude them.
Clear address search, expand distance, remove exact beds or baths, broaden size and price ranges, and check sold-date or listing-status filters.
Distance removes unexpected properties
Distance filtering depends on valid subject and comp coordinates. Results without usable coordinates cannot satisfy the calculation. Confirm the subject location and try a wider distance before assuming no comparable exists.
Ranking changed without a new run
Saving settings under Settings → Rankings re-ranks existing comps on reload. If the order changed:
- Look for the Custom scoring indicator.
- Check the selected comp type’s enabled criteria, weights, and tolerances.
- Clear any manual column sort.
- Confirm you are viewing the same run snapshot.
Ranking changes do not mean new source properties were collected.
A fresh run looks the same
ReiSearch warns when you refresh within 24 hours because another run may not change much. Check run time, filters, and ranking before assuming the refresh failed.