[SOLVED]. API poll doesn't un-SET or populate child expressions (bare metal install)

[gwp1]

This is tough to explain, saying that right up front.

HTTP Request GET to Ambient Weather API, capturing to ambient_api and the subsequent expressions for temp, UV, wind, etc. . It should be noted, this ruleset has been in place for months, working as intended.

Disclaimer: I'm not pointing the finger at build 22021/22022 - but - using Tech Support rule #1 ("What changed?") it's in my peripheral vision.

Initial Observations:

• Upgraded from build 22004

• The ruleset runs every five minutes, like usual, resetting when the call is done. It is NOT updating the global expressions. The data is stale. It is also not returning NULL (which sometimes the Ambient API flakes and does that and I have failover rulesets to cover that.)

• Running the ruleset manually with the Reset button returns either an API 429 or 421 error, NULL as the result which triggers the failover as it should.

• On the next scheduled run the ruleset the API errors go away and we're back to the first bullet point.

• rolling back to build 22004 resolves the issue, everything goes back to working as intended, proven multiple times yesterday working thru the unrelated issues build 220021 had.

• Other APIs appear to be working as intended. UPDATE: this is not the case, all three APIs are behaving the same as far as updating their children.

Troubleshooting:

• I've copied the URL directly from the original ruleset and run it in a browser, no 429/421 errors no matter how many times I hammer on it.

• I've copied the URL and used it to create a duplicate replacement ruleset.

• Copied a working non-Ambient ruleset and updated the URL to make it an Ambient ruleset, which has picked up it's own oddities (noted below).

Current oddities:

• The replacement ruleset runs on five minute schedule - and stays SET, prohibiting it from doing anything at the next five minute interval. (This only appears in build 22022.)

• because of the above, I turned off that ruleset and re-enabled the original which immediately performed the GET 100% as expected - only to fail to update the child expressions after updating the ambient_api expression on the very next scheduled run.

Logs:
The first screenshots are the scheduled run at 0900 ET.

The next screenshot is the manual (via Reset) at 0905 ET

The next screenshot is the scheduled run at 0910 ET after the last run set the ruleset to SET

The last screenshot is the rulesets including the new one that is stuck in SET

I have the actual logs that go with the screenshots and can provide if necessary.

UPDATE: solved here https://smarthome.community/topic/872/expressions-not-auto-updating-when-dependencies-change-22022/8