Pulse package execution timeout
I initially had this posted in the Pulse forums here, however this may be a more appropriate place.
Is there a timeout setting for package execution? One of our users started a package execution that updated a cube rule, triggering TM1 to reprocess the cubes feeders. The feeders took ~31 minutes to reprocess (and they did so successfully with the correct rule change), but Pulse seems to think the package is still executing.
We had to restart Pulse Application Server to attempt to execute the package again.
I’ve confirmed the following SessionTimeout timeout setting that should be at least an hour:
Pulse version 6.2.20230706 when first reported. (we now have Pulse Version 6.2.20230720 deployed, but haven't attempted issue replication)