Craig Patrick created NIFI-14924:
------------------------------------
Summary: Updating Process Flows via Registry which fail do not
output errors to UI
Key: NIFI-14924
URL: https://issues.apache.org/jira/browse/NIFI-14924
Project: Apache NiFi
Issue Type: Bug
Components: Core UI
Affects Versions: 2.0.0
Environment: All
Reporter: Craig Patrick
When updating a process flow via the NiFI Registry recently, I came across an
issue where the update process would stop at 80% with the UI stating "Process
version has been changed". This was an issue as the process had not been
changed, and no matter what I would try it would not pass the 80% mark.
The issue turns out to be that it was failing (information found in logs) but
this was not being output to the UI and so the user has no idea what the
problem is or how to fix the update issue.
The error noted in the logs for this particular incident was:
{code:java}
2025-08-28 12:57:08,924 ERROR [Process Group Update Thread-1]
o.apache.nifi.web.api.FlowUpdateResource Failed to perform update flow request
java.lang.IllegalStateException: Cannot update parameter
'bi.pgp.keyfile.location' because it is referenced by
StandardControllerServiceNode[service=StandardPGPPrivateKeyService[id=01981005-73db-1be6-e257-965e70cf6045],
name=StandardPGPPrivateKeyService, active=true], which currently has a state
of ENABLED {code}
The error message in this instance should be updated to the UI in order for the
user to be able to see why the update failed without having to dig through
logs, especially for instances where the developer may not have access to the
NiFi logs
*it's also worth noting, that in this instance the updated processor had
nothing to do with the processor which was throwing the error and they were
completely separate so this may also be an issue*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
