The RevisionCloud Procedure is parametric ...therefore requires a specific
sequence of input events in order to produce the desired modifiable outcomes.
Any violation of the methodology will either wait, stop or loop the process.
Sooner or later everyone experiences similar issues with one or more of the many parametric tools.
Usually, the easiest solution is to utilize the current version's Help Resources
in order to review the proven input methodology for the offending procedure(s).
If this fails to resolve the problem, then look to the active/ dynamic file structure.
Often I have found that a simple Save & Relaunch will right an otherwise sinking ship : )