@bryan_333, and for anyone else interested – Some background on this:
The root cause here was related to conditional states on elements, rather than with API calls in general. I spent some time this morning looking for any other possible manifestations, and it seems likely that the only way to trigger it was the situation you ran into here where a property set by a conditional state with an API value in it wouldn’t be applied. In particular, the scenario to trigger the issue was:
- an element’s conditional state set one of its properties to a dynamic expression which contained an API call
- the API call was done on the server (browser-only calls weren’t affected)
- the API call result hadn’t already been loaded by something else on the page by the time the state activated (cached API calls weren’t affected)
API calls performed from anywhere else (workflows, non-state dynamic expressions, etc.) would not have been affected in any direct way. In theory it’s possible for this to have affected workflows indirectly, if the workflow used a group as a data source and the group’s data was set by an affected conditional state with an API call in it. In this case, the workflow would have been run as usual but would have seen the same value as was displayed in the group. If the group value was displayed to the user, that’s probably what they intended; if it was invisible it may be worth checking up on.