Something that I have intended to post a long time ago. If a user has report with DRWS's that reference an invalid element 2 things happen 1) Users experience the circle of death and reports don't necessarilybrefresh properly 2) The tm1server.log records an MDX error with the offending invalid element. I'm assuming this is because it's causing an error within the engine.

However the users receive no notification, perhaps because the rest api is not sending back an error to PAfE?

If there a setting somewhere that enables notification to the user?

Hi John,

we have seen similar behavior in PAfE where an error is recorded on the TM1 server side, while the user interface does not provide any meaningful feedback and may remain in a loading state.

I would also be interested in understanding where the error gets lost in this case. If the invalid element results in an MDX error in the TM1 server, does the REST API actually return the error to PAfE and PAfE fail to display it, or is the error handled/hidden somewhere before it reaches the client?

It is also possible that the error is actually recorded somewhere in the PAfE logs, but since no meaningful error message is presented to the user, the user has no way of knowing what went wrong and may simply ignore the issue or assume that PAfE is still processing.

A clear error message in PAfE would certainly be preferable to leaving the user with an endless loading indicator.

Has anyone checked the corresponding REST API response and the PAfE log for this scenario?