the behavior you describe is usually tied to refresh settings + supported field types + rule interactions, not just “field change” by itself. In Constellation, the refresh request is expected to trigger when the configured form-refresh field changes, but there are instances where the call does not happen or stops happening because of view/rule conditions or platform behaviour.
The most common reasons are:
- The field is not configured refresh trigger fields on the flow action
- The field is an embedded page, complex field, or list, which is not always supported
- If the view contains When rules, calculated fields or visibility/disabled/required logic, they might suppress or alter the refresh behaviour.
If it works in some screens but not others, that is usually related to a configuration difference.
Also, Pega does not refresh a data page more than once per interaction, so later edits in the same cycle may not generate another API call.
compare the working and non-working case types for differences in the trigger field type, refresh settings and view logic. If there are When rules involved, try replacing them with Custom Conditions and retest.