I was successfull in recreating my experimental setup and the issue. With
what you told me about disabled processors, I understand know that a
service restart would be unhindered by the misbehaving processor. The
restart was successful and the restart on my original experimental setup
was also successful. I could then access the PG and delete the
InvokeScriptedProcessor.
If anyone ever comes across this issue, keep in mind that it may have only
worked because I was able to disable the entire PG (including the
misbehaving one). I believe that the error only propagated to the point
where my Parameter Context was defined as this processor was nested 2 or 3
levels deep. A diagram will help:
NiFi Flow [still accessible]
/ PG (that defines a PContext1) [cannot access]
/ PG 1 (with PC1)
/ PG 2 (with PC1)
/ InvokeScriptedProcessor (misbehaving)
I could still access any other PG from the root PG. I don't know if this is
relevant but it was part of my setup.
Thank you Mark.
--
Best regards,
*Santiago*
