The xpp process status api call returns 404 immediately as soon as the process is complete and
for some the process id is active for more than 12 hours as well.
We have noticed lot of inconsistency in the time the process ids are active.

Steps to reproduce:
We can make an async call to any of the xpp apis like compose job api by passing the nowait as true.
In response to this api call we will get a process id
To check the status of the process id we have to make another xpp api call that is process status call. This api call returns the status of the process id.

Expected Output:
Once we make a call to the process status api, we should get the status of the process id and the process id should be active for a specific fixed time.

Actual Output:
We are noticing lot of inconsistency in the time the process id remains active.
For some the process ids are active for more than 12 hours, and for some the process ids are active for only few minutes.
The once that expiry within few minutes are causing problem for us,
since we have a scheduler which is going to monitor the process status by calling the api in specific interval of time.
If the process if expires without few minutes, we start getting 404 issue and our entire flow fails