Planning Analytics

Hey everyone,

Running into an issue where, when I run a process from an action button in PAW 2.0.96 (and other earlier versions), a notification pops up that the process was aborted after 10 seconds, but there are no error logs and the process runs fine.

Funny thing is, if i have another browser window open on the Admin pane, auto-refreshing the server thread monitor every few seconds, or if I have a cube view on the PAW tab where the action button is and set it to refresh every 5 seconds or so, then the process runs fine and notifies, after the ~30 seconds it takes, that it has run fine.

Is there some esoteric timeout setting I am just not configuring that needs to be configured that is responsible for this? Seems like there is an issue with PAW just NOT keeping the connection with TM1 open, or perhaps more likely the browser not keeping the connection with PAW open, for anything longer than 10 seconds in this instance.

Thanks,

Hey everyone,

Running into an issue where, when I run a process from an action button in PAW 2.0.96 (and other earlier versions), a notification pops up that the process was aborted after 10 seconds, but there are no error logs and the process runs fine.

Funny thing is, if i have another browser window open on the Admin pane, auto-refreshing the server thread monitor every few seconds, or if I have a cube view on the PAW tab where the action button is and set it to refresh every 5 seconds or so, then the process runs fine and notifies, after the ~30 seconds it takes, that it has run fine.

Is there some esoteric timeout setting I am just not configuring that needs to be configured that is responsible for this? Seems like there is an issue with PAW just NOT keeping the connection with TM1 open, or perhaps more likely the browser not keeping the connection with PAW open, for anything longer than 10 seconds in this instance.

Thanks,

Hi Tom,

The action button in PAW make async REST API calls to TM1, so unless there is a very low timeout set (e.g 10 seconds) this should not happen.  Note that the PAW cube viewer and most other interfaces in PAW also make async API calls to TM1 as well.

I might suspect there is some network infrastructure (software or hardware) between PAW and TM1 that is closing the connection.

Also, just to clarify, this is a PAW action button on a PAW book?  Not a Websheet button on a Websheet in a PAW book?

Hey everyone,

Running into an issue where, when I run a process from an action button in PAW 2.0.96 (and other earlier versions), a notification pops up that the process was aborted after 10 seconds, but there are no error logs and the process runs fine.

Funny thing is, if i have another browser window open on the Admin pane, auto-refreshing the server thread monitor every few seconds, or if I have a cube view on the PAW tab where the action button is and set it to refresh every 5 seconds or so, then the process runs fine and notifies, after the ~30 seconds it takes, that it has run fine.

Is there some esoteric timeout setting I am just not configuring that needs to be configured that is responsible for this? Seems like there is an issue with PAW just NOT keeping the connection with TM1 open, or perhaps more likely the browser not keeping the connection with PAW open, for anything longer than 10 seconds in this instance.

Thanks,

Hi Stuart,

The environment is an Azure VM which is hosting PAW, TM1 and Cognos Analytics.

ProxyTimeoutSeconds is set to 900.

This is a PAW workbook with a PAW action button, no websheets involved.

Thanks,

Tom

Hi Tom,

The action button in PAW make async REST API calls to TM1, so unless there is a very low timeout set (e.g 10 seconds) this should not happen.  Note that the PAW cube viewer and most other interfaces in PAW also make async API calls to TM1 as well.

I might suspect there is some network infrastructure (software or hardware) between PAW and TM1 that is closing the connection.

Also, just to clarify, this is a PAW action button on a PAW book?  Not a Websheet button on a Websheet in a PAW book?

Hey everyone,

Running into an issue where, when I run a process from an action button in PAW 2.0.96 (and other earlier versions), a notification pops up that the process was aborted after 10 seconds, but there are no error logs and the process runs fine.

Funny thing is, if i have another browser window open on the Admin pane, auto-refreshing the server thread monitor every few seconds, or if I have a cube view on the PAW tab where the action button is and set it to refresh every 5 seconds or so, then the process runs fine and notifies, after the ~30 seconds it takes, that it has run fine.

Is there some esoteric timeout setting I am just not configuring that needs to be configured that is responsible for this? Seems like there is an issue with PAW just NOT keeping the connection with TM1 open, or perhaps more likely the browser not keeping the connection with PAW open, for anything longer than 10 seconds in this instance.

Thanks,