I am not familiar with IFS Cloud but in previous versions, once started, a job can only be stopped by killing the Oracle Process that’s running via the Monitoring\Database Sessions screen.

This then gets messy as you have then manipulate some of the underlying tables to fix the reported job status (killing the process breaks the normal queue status update handling in IFS).

So You need to be really sure you want to go down this road (and know how to fix the resulting table mismatches).

Are you sure it’s still running? 

Given the time elapsed, Oracle may well have terminated the job as having run too long. IFS wouldn't know and so the status will remain as running.

Check the database sessions to see whether it is active or not.

I would recommend you get some help from IFS Support if this is the case.

Hi ​@KIMKIMANDREW 

Thank you very much. I will check whether it is still running.

Best regard,

Feng