When debugging a flow service, on calling another flow service an error dialog pops up with a null pointer error. No other information is displayed. On dismissing the dialog, the debugging session is terminated. This does not occur for calls to all flow services.
Running the same flow service does not cause the bug.
If I select ‘Validate Input’ and save the flow service that was not able to be called, the null pointer error does not occur. If I then deselect ‘Validate Input’ and save, the null pointer does not occur.
I ran all three scenarios with the same pipeline information.
Given the above I assume it is the act of saving the file that causes the null pointer to disappear.
Why does the error occur in the first place and why does saving the file fix the issue?