If the FPR publisher starts, but fails to upload to the Fortify server, the Jenkins job is not flagged as failed or unstable.

When our token expired, the uploads to the Fortify server would time out and fail, but the Jenkins jobs are still marked as successful. If publish is selected for a job and that step fails, then the job should not be marked as a success.
Perhaps a configurable option to either fail the job or mark as unstable is needed.