Moved to ZBXNEXT project.

It is not a feature request.
In 4.0 Check now button is clickable and displays successful request sent even for active checks (which is not supported by design.)

The "Check now" (mass select) is working for such items like SNMP traps and Zabbix trapper and "Request sent successfully" message is misleading.

I do believe it is bug also.

There should be no way to apply 'check now' to items that don't support it. Really misleading.

Thanks for your comments. Moved back to ZBX project.

As discussed, expected solution should be like this:
1) Don't perform Check Now in item list, if at least one unsupported item is selected. Show error message about it.
2) Hide Check Now button in item list, if only templated items are filtered.

Valdi, thank you so much for listing the planned changes.
Perhaps it would be better to disable the button instead of hiding it? Disappearing UI elements can be very confusing, and the concept of disabling the buttons is well established & working in the entity lists.

Hi richlv,
You may be right, that disappearing button is not the best solution, but disabling it in some cases, while not disabling in others, will also be inconsistent. On the other hand creation of "perfect" disabling rule, will be JS script heavy, and we would like to avoid it, at least in scope of this task.
As a result, we agreed to keep the button for any items, and only have error message, returned by API, when Check Now operation is performed for unsupported items.

That also sounds like a great solution - it will always be clear what happened or didn't happen.

FIXED in development branch svn://svn.zabbix.com/branches/dev/ZBX-14928

Will this implementation also enable active agent remote execution?
Currently Zabbix agent time-outs (which should be kept low for good reasons) may conflict with remote execution tasks.

No, it's unrelated issue.

My apologies! I haven't found any related ticket. But now, after having searched again before creating a feature request, I found ZBXNEXT-297. Sorry! I should have searched better.

Fixed in:

• 4.0.3rc1 r87446
• 4.2.0alpha2 (trunk) r87448

Updated documentation:

• What's new
• Known issues

Can you please explain why this feature isn't supposed to be used for active checks?

Brett, because it's not implemented for active checks yet.

 Ironically, I used this new feature yesterday for the first time, before seeing this in the release notes for v4.0.3 today. FWIW, it does work (v4.0.2).   It is a "agent (active)" type item with a 1 hour interval.  Selected the 'check now' button and they all updated within ~2 minutes.

Wow, bspach can you stable reproduce active agent check now with 4.0.2?