Forum Discussion
Something went wrong while refreshing or saving existing dataflows
The microsoft thech support fixe the issue.
Now I see more detailed logs.
And they wrote me this:
If you set up a separate schedule for the linked dataflow, dataflows can refresh unnecessarily and block you from editing the dataflow. There are two recommendations to avoid this issue:
- Avoid setting a refresh schedule for a linked dataflow in the same workspace as the source dataflow
- If you want to configure a refresh schedule separately, and want to avoid the locking behavior, separate the dataflow in a separate workspace.
Anonymous
I am sorry that I cannot reproduce the error on my side. However, I have some suggestions for you:
1. Checked the status of your gateway, is it online or offline.
2. Any other details about the refresh fail except the ids?
Best,
Paul
Hello!
These dataflows don't use my gateway. However, it works and it is online.
When I try to refresh dataflow, I recieve error:
| Run time | Dataflow name | Dataflow refresh status | Entity name | Start time | End time | Entity refresh status | Error |
| Invalid date | SNOW_2020 | Failed | Failed | There was a problem refreshing your dataflow. {"RootActivityId":"ea5b92d5-8238-a51d-64f0-88a7594e335d"} |
By the way, earlier I have been recieveng another error:
| Run time | Dataflow name | Dataflow refresh status | Entity name | Start time | End time | Entity refresh status | Error |
| 01.10.2020 10:32 | SNOW_2020 | Failed | Failed | There was a problem refreshing your dataflow. {"RootActivityId":"6723826d-f082-470a-a1a3-6bc240fffc6f"}
|
The microsoft thech support fixe the issue.
Now I see more detailed logs.
And they wrote me this:
If you set up a separate schedule for the linked dataflow, dataflows can refresh unnecessarily and block you from editing the dataflow. There are two recommendations to avoid this issue:
- Avoid setting a refresh schedule for a linked dataflow in the same workspace as the source dataflow
- If you want to configure a refresh schedule separately, and want to avoid the locking behavior, separate the dataflow in a separate workspace.