Personally, I think it's a bug in the way they wrote the API as a "user friendly" version. At least they didn't think through a more complete use case scenario about how it would be used. The actual Power BI API that triggers the refresh is a two-part solution one API call triggers the refresh, but then you have to follow behind it with a get refresh status API that takes the refresh ID of the step before and checks to see the status of the refresh. They only made the trigger available, not the check status.
With what we have to work with today, I think the easiest solution (aside from getting a custom connector setup to run your own API commands) would be to look at the refresh history of the dataset, and see how long it takes to refresh, then using a delay action in power automate take the refresh duration and add 30s to a minute more to it and have power automate "wait" that long after triggering a refresh before moving on to the next steps.
you can vote for or submit this "idea"... should really be a bug report but... on ideas.powerautomate.com
@Wilky333 @mohindar