David Blain

> Hello! Thank you very much for taking the time to look at the code and making this suggestion. I tried to reduce the `check_interval` to 5, unfortunately it did...

@Ohashiro also thank you for investigating this thouroughly. It would also be nice to have a unit test which reproduces this behaviour, so on fist invocation raising an PowerBIDatasetRefreshException, then...

> Hi @Ohashiro, thank you for bringing this up and creating the PR to address it. After reviewing the conversation, I see the issue lies in `get refresh history` function...

> Hello! @dabla thank you for your investigation and suggestion! > > Regarding your first point: > > > I also went back to the code and I still don't...

> Btw, I just (locally) implemented your refactor and the separation between the 2 flows (refresh trigger and get refresh status) in 2 deferrable triggers seems to let enough time...

> However, it should be possible to retry the operator "execute" function without retrying the task, as done in DmsStartReplicationOperator You're right about the Xcoms being flushed when a task...

The separation of the 2 flows handled by the PowerBITriggerer is a good thing indeed, so the effort there is not lost and is in fact a cleaner design. Now...

> Hi @dabla I opened a PR with the following changes: the separation between the 2 flows and the retry on the func `fetch_refresh_status_and_error`. I'd be happy to have your...