Why doesn't an item that becomes "Unsaported" get activated when forced?

Question

Zabbix

I set up monitoring of the database
I set up unixODBC, DB connections, the clients themselves (oracle) I
set up the item on the Web. crashed with error "Cannot connect to ODBC DSN:[SQL_ERROR]:[01000][0][[unixODBC][Driver Manager]Can't open lib '/usr/lib/oracle/11.2/client64/lib/libsqora.so .11.1' : file not found]|"
I faced similar problems back on 2.0.8 because I quickly figured out how to solve this issue.
I run ISQL -v TEST_BD under the zabbix user, everything works.
On the web, the item has fallen into UNSAPORTED status.
After I corrected everything, I try to activate it again, but it immediately falls from the "Deactivated" status to the "UNSAPORTED" status. There is only one entry in the log about the item falling into an error, but there are no retries.
Maybe someone came across and figured it out? why does zabbix behave like this? Or maybe I'm not correctly activating the fallen items?

Answer 1

Zabbix Server reactivates Unsupported Items on its own after 600 seconds.
This is an adjustable setting.
Administration -> General -> Other (in abort) -> Refresh unsupported items (in sec).
Zabbix Proxy reactivates Unsupported Items after 10 minutes. Proxy does not regulate this.
https://www.zabbix.com/documentation/3.0/manual/we...