UWS: delay destruction of a job returns an error if new destruction datetime is in the past

[almicol]

LOW PRIORITY I have a UWS job in PENDING status; If I change the destruction date to a future date, the system works as expected. If I change the destruction date to a past date, the system returns a VOTable with the error message: Incorrect job ID! The job "1513770746650" does not exist in the jobs list "async". And that is true, the job is no longer listed in the jobs list; as if got probably destroyed.

Would not be better to then return the jobs list instead of an error?

Thanks!