Thanks for reporting. Will be fixed in next patch release.

Hello@robinshen,
I checked at the new version, the unrecommend function is still not in sync logically.
I also tested different logics on my PC and found that saving before running the listener gives better result.

plugin

try {
	// do something
} catch(Throwable t) {
	build.setStatus(SUCCESSFUL)
}

recommend function

BuildManager.instance.save(build);
for (BuildListener listener: PluginManager.instance.getExtensions(BuildListener.class))
	listener.buildRecommended();

The end result I want is for the recommendation to fail and the status to return to SUCCESSFUL.

This has been fixed in 15.0.24:

Build will be saved after calling listener, and if there are exceptions in listener code, the recommend/unrecomment status will not be written to database.

Looks like you didn't read my request.
"I also tested different logics on my PC and found that saving before running the listener gives better result."

The last task run should be the undo task in the listener's catch block.

I read your point, but that is not a good practice (change status and revert it back upon failure). The most straightforward and safe approach is to save the build only after all listener code finished without errors.