Forum Discussion
Service Refresh timing out
Ok the issue is not about the size of the model, the error suggest reducing the size because it's usually one of the reasons for a timeout. The error message sounds like the problem it's that the refresh process takes too much. It can be an issue in the Power Query transformations (steps or connector) or the Dynamics Server instance is not responding fast at some time in the day. Some connectors will let you have a parameter of timeout like Sql.Databases. I'm not familiarized with the one you are using right now but that might help. If you can increase the timeout connection or command for the query that might help. Even though it's weird that the server takes a lot of time to reply a few rows. It can also be an issue of the dynamics server.
I hope that helps,
ibarrau , here is the error, it is cloud, as you can see, its a very small dataset. On some days it will refresh ok and others I get failures. We can log a ticket with MS to look into it but just wondered if anyone had any thoughts before that. I can't see any reason for getting these issues with a report with such a small data set thats cloud.
Ok the issue is not about the size of the model, the error suggest reducing the size because it's usually one of the reasons for a timeout. The error message sounds like the problem it's that the refresh process takes too much. It can be an issue in the Power Query transformations (steps or connector) or the Dynamics Server instance is not responding fast at some time in the day. Some connectors will let you have a parameter of timeout like Sql.Databases. I'm not familiarized with the one you are using right now but that might help. If you can increase the timeout connection or command for the query that might help. Even though it's weird that the server takes a lot of time to reply a few rows. It can also be an issue of the dynamics server.
I hope that helps,
Thanks, thats really helpful. I will go back and review the Dynamics connectors and any transformations incase thats where the problem may be. Thanks