metatogger remote name could not be solved

Then add a Delay, I've chosen 30 seconds.īetween the 'set convertError true' and convert action, add a parallel branch and copy paste the 'set convertError true' action there. Set it to true and add the runAfter parameters: timeout and error, remove succeeded In my example its called 'convertError', rename the set action to: set convertError true. In this Loop you'll need to add the Convert action.Īfter the convert action set a Bool Var, which you need to initialize beforehand.

Timeout: P7D - (This means, the loop will loop for 7 days) It took my Do Until Loop 38 minutes and 31 tries to finally convert the file. I'm currently trying the Action until it works. Word file has two text boxes to change and background as watermark. What other connector should I use instead of OneDrive for Business?

Microsoft's technical support did not even make a notification within three days. I do not see any rule as to why flow starts once and then does not. 'message': 'The remote name could not be resolved: ''',

The remote name could not be resolved: '' Only if failed all times then you can quit/report an error to your users.Problem in converting Word to PDF with One Drive Businnes.įlow first fills the Word file with two variables, saves it, converts it to PDF, and finally sends it in a message. Handle known exceptions, wait a little (say 1000 msec) and try again (for say 3 times). What I'd suggest to always wrap that (network related) code in a loop with a try/ catch block (as also suggested here for other fallible operations). It may happen, there isn't much you can do. Unfortunately HResult is generic, however you can determine the exact issue catching HttpRequestException and then inspecting InnerException: if it's a WebException then you can check the WebException.Status property, for example WebExceptionStatus.NameResolutionFailure should indicate a DNS resolution problem.

It's probably caused by a local network connectivity issue (but also a DNS error is possible).

Metatogger remote name could not be solved