Hi, When job proxy expires, its manager dies, but the job itself keeps running. There is no way to check its status, and even when job is submitted with save_state=true, the restart does not work. Also, audit never puts the record of completed job into the database.
On the other hand if I submit two jobs, first one with long proxy, and second job with shorter proxy, even when second proxy expires I can still query the job as long as first proxy is valid and job manager is running. GRAM4 never had this problem, even when proxy expires job status is still available and it is properly audited. Is it possible for gram5 to have the same behaviour? At least being able to restart job manager after proxy expiration and have it properly audited. Cheers, Yuriy
