I had this problem too and blamed it on a new camera that I was testing. I was not even able to start the PAA process as "start" was greyed out. My FOV was much larger than the minimal FOV so did not make sense.
I was running a nightly build. The next day (26th Sept) I updated the nightly build and tested using my normal camera and at least the start button in the GUI is usable to start the automated process. However the FOV disabled warning persists.
Unfortunately I have not had a chance to test it in the field.
As the latest updates have not resolved the erroneous FOV related PAA disabled warning, the problem is not solved.
Cheers

Read More...