Using PagerDuty Plugin 0.2.4

PagerDuty Incident Trigger is set up as one of the "Post-build Actions" for a Jenkins job with these settings enabled:
1) Trigger Incident on FAILURE job result
2) Resolve on BACK-TO-NORMAL
Jenkins job failed in one of the runs, thus creating a PD incident successfully. On the next run, the job itself succeeded however it failed to resolve the incident due to some connection issues. Failure to resolve a PagerDuty incident as a "Post-build Action" marked the Jenkins build result itself as a failure. This needs to be fixed because any downstream jobs scheduled to trigger on FAILURE of this job can undesirably get triggered just because of failure to resolve PD incident which is just a post-build action.