Hi Walter,
I assume you are seeing messages somewhat like:
4:27:57,365 INFO [com.netapp.wfa.engine.reservations.ReservationsDaoImpl] (EJB default - 7) Purging obsolete reservation - job status 'COMPLETED' , TTL '14400000'
04:27:57,381 INFO [com.netapp.wfa.engine.reservations.ReservationsDaoImpl] (EJB default - 7) 0 rows purged
04:27:57,381 INFO [com.netapp.wfa.engine.reservations.ReservationsDaoImpl] (EJB default - 7) Purging obsolete reservation - job status 'FAILED' , TTL '172800000'
04:27:57,397 INFO [com.netapp.wfa.engine.reservations.ReservationsDaoImpl] (EJB default - 7) 0 rows purged
04:27:57,397 INFO [com.netapp.wfa.engine.reservations.ReservationsDaoImpl] (EJB default - 7) Purging obsolete reservation - job status 'CANCELED' , TTL '172800000'
04:27:57,412 INFO [com.netapp.wfa.engine.reservations.ReservationsDaoImpl] (EJB default - 7) 0 rows purged
04:27:57,428 INFO [com.netapp.wfa.engine.reservations.ReservationsDaoImpl] (EJB default - 7) Purging obsolete reservation - job status 'OBSOLETE' , TTL '172800000'
04:27:57,428 INFO [com.netapp.wfa.engine.reservations.ReservationsDaoImpl] (EJB default - 7) 0 rows purged
These absolutely do not mean that the job has failed. If by any chance, there were failed jobs WFA server cleans up its reservation after a default of 2 days (screenshot above). Similarly for other job statuses.
Let me file an internal issue to improve this log message as it is confusing.
Thanks,
Shailaja