There is no Repository Process. There are background jobs that run periodically, but there is no specific Repository Process.

Every night timer policies are checked to see if they have expired on an asset, and if they have then that policy is executed against the asset. So it all depends on the configuration of the timer policies on an asset. Each asset can have a different set of timer policies that are configured to run at different dates. The timer policies are configured in the assets lifecycle.

That's not a process. It is a user. It is the user that we use for background jobs since there is no actual user making the changes at that time. But we have to have some user in the change metric, so it is the Repository Process user.

As I stated  there are pending policies or timer policies. These run when their timer has expired. Pending policies actually run often. They are scheduled whenever a policy runs and it returns that the policy is still pending, meaning it can't complete at this time, come back and look later. Pending policies are executed every 30 seconds until they indicate they are done. This is meant for short term waiting on data.

Timer policies are scheduled for some future date, in days, weeks, etc. Never less than one day. Every night there is check for any timer policies that have expired in the last day, and if so those policies are then executed. They could then either complete or they could be rescheduled for another future date.

There is no viewer that can display what policies are scheduled and for when.