← All articles

SAIL / DEBUGGING

Appian refresh behavior: practical patterns

In Appian interfaces, a value can look stale even when the expression is correct. The first debugging question should be what causes this value to recalculate? rather than whether the formula itself returns the expected result.

A systematic diagnosis

  1. Identify which local variable or rule input supplies the displayed value.
  2. List the inputs that should cause it to change.
  3. Check whether the local variable is intentionally cached or set to refresh.
  4. Check whether a save operation updates the dependency that drives the calculation.
  5. Compare the interface evaluation with the same rule executed in isolation.

Illustrative expression

a!localVariables(
  local!selectedId: 1,
  local!details: a!refreshVariable(
    value: rule!DEMO_getDetails(local!selectedId),
    refreshOnVarChange: true
  ),
  /* Render an interface referencing local!details here */
  local!details
)

This is a simplified expression, not a complete production interface. Actual behavior depends on which variables are referenced by the expression and how users modify them.

Common pitfall

If the data source changes externally without any dependency changing in the interface, a variable may not recalculate when expected. Consider whether an explicit refresh trigger is needed, and verify the behavior against your Appian version.

Takeaway

Debug the dependency chain before rewriting business logic. Refresh bugs are often lifecycle misunderstandings, not calculation mistakes.