I am not sure, if this is bug, or I do not see some mistake (excuse me, if latter the case):

Steps to reproduce:

• HTTPS/GET agent item with URL provided by macro {$UU.CLOUD.APP.C3OR.ACCESS.URL.C3}
• required status codes: 100-599
• update interval: {$UU.CLOUD.ZBX.INTERVAL.LLD} (set to 15m)
• timeout: 15s
• preprocessing to parse expected valid JSON from HTTPS response:
   

  {"schemaUri":"ues:SYSTEM:UU.OS.APPLICATION/ERROR_MESSAGE-SCHEMA-V3","id":"047d647cd7295780dfc33ca6ef3898be","timestamp":"2022-03-27T22:43:17.304Z","message":"Missing authentication data.","kind":"CLIENT","code":"UU.OS.APPLICATION/E003-NOT_AUTHENTICATED","attributes":null,"detailMessages":null}

Macro in preprocessing is set to 1d (doublechecked).

I was testing trigger checking if last value is 0 by changing URL (in macro above) to invalid (to test timeout). Last stored value changed to 0 and trigger fired. Then I changed URL macro back to valid one, to make the trigger close the event.

Result:
**

Last stored value is not switching back to 1.

To ensure JSON is not changed or HTTP request is not outing time, I created the same item clone, but without preprocessing (it is returning still the same JSON, just timestamp is changing, it is not becoming not supported), and tested possible timeout also by curl - it is taking much shorter time than configured timeout 15s.

But despite that all, the item with preprocessing stopped to update on 0:

Expected:
If I see everything correctly, last stored value should be now set to 1.

I am not aware of any change potentially causing this, and previously it workerd, as seen in item history screenshot.