Forum Discussion
DM_GWPipeline_Client_MaxPacketLimitReached
I found the root cause of this errorin my situation. There was a fact table with more than a million records set to Dual storage mode, when this table was set back to direct query we no longer received the error.
I believe it has to do with how the service handles queries when importing a table and being able to break the results down into sets less than 1M records whereas the dual storage mode is intended more for dimensional (i.e. smaller) tables and this causes the error as it tries to refresh the dual mode tables.
I found the root cause of this errorin my situation. There was a fact table with more than a million records set to Dual storage mode, when this table was set back to direct query we no longer received the error.
I believe it has to do with how the service handles queries when importing a table and being able to break the results down into sets less than 1M records whereas the dual storage mode is intended more for dimensional (i.e. smaller) tables and this causes the error as it tries to refresh the dual mode tables.
In my case, the problem has been solved today by replacing a SUMX/FILTER query by a CALCULATE query.