When there is a perceived error in an inline pipeline script, the dynamic messaging related to script approval does not update.

For me, I noticed when modifying a previously approved inline script that uses a shared library. The classes from the shared library are not recognized by the editor (this is "normal"), resulting in a validation error. The approval text below the editor remained at "This script is already approved" instead of updating to show the expected approval button.

As a workaround, the script could be approved in-place by saving the change and then opening up the config again. The updated script was loaded, along with the expected approval state description. (The new script was also available for approval from the script approval UI.)