Home →
Troubleshooting →
@RISK for Excel: Simulation →
**"Found invalid formula ... Continue without Smart Sensitivity Analysis?"**

**Applies to:** @RISK 5.x–7.x

When I start a simulation, I get the error message

Found invalid formula ... Continue without Smart Sensitivity Analysis?

Or,

The reference '...' in '...' has an OFFSET or INDIRECT, whose precedents cannot be traced.

Continue without Smart Sensitivity Analysis?

Smart Sensitivity Analysis was introduced in @RISK 5.0. It's described in the article Precedent Checking (Smart Sensitivity Analysis).

As @RISK traces back from your @RISK outputs to your distribution functions, along the way it may find an invalid Excel formula. You should fix the formula, using Excel's Find feature to locate it if necessary, and re-run your simulation. (Instead of Find, you can use the location given just before "has an OFFSET". That will be either a cell reference or a defined name; you can access defined names in Excel through Formulas » Name Manager (in Excel 2003 and below, Insert » Name » Define).

Certain formulas are correct Excel formulas, but Smart Sensitivity Analysis cannot work with them. Please see Precedent Checking for the list. If the message identifies one of these formulas, either change the formula (if possible) or disable Smart Sensitivity Analysis on the Sampling tab of Simulation Settings. If the formula is actually correct, and does not fall in any of those categories, please contact Technical Support at support@palisade.com.

The choice of enabling or disabling Smart Sensitivity Analysis can be made for each workbook, and you can also set it in Application Settings to apply to new models.

These settings are available in @RISK 5.0.1 and above and in all releases of @RISK in The DecisionTools Suite 5.x. If you have @RISK 5.0.0, Smart Sensitivity Analysis is always enabled. You can upgrade to the current version to gain many other features as well as the ability to control Smart Sensitivity Analysis. Please visit http://www.palisade.com/Updates/ or contact your Palisade sales manager to request an update to the latest version of @RISK.

**See also:**

The RiskMakeInput function is treated as a special case, and the above technique will not work for it. See "Found invalid formula ... Continue without detecting RiskMakeInput precedents properly?"

Last edited: 2017-02-17

This page was: Helpful |
Not Helpful