Power Automate Desktop中Get Emails(V3)空URI错误求助

• 桌面流流程：获取API信息→提取邮件中的候选人ID进行后续处理→将API数据写入Excel，API部分无报错
• 故障现象：执行Get Emails V3步骤时抛出空URI错误，该流程在4月10日前可正常运行
• 已排查操作：检查连接器连接状态、流程代码，新建流后问题依旧；但邮件发送功能可正常使用

错误堆栈信息 #

Correlation Id: 8f39e7ab-b465-4dd2-85f4-508d3e170846
System.UriFormatException: Invalid URI: The URI is empty.
   at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
   at Microsoft.Flow.RPA.Desktop.Robin.Connectors.Execution.RequestBuilders.BaseConnectorRequestBuilder.GetActionPathFromApimLocation(String connectionId, String location)
   at Microsoft.Flow.RPA.Desktop.Robin.Connectors.Execution.RequestBuilders.PPApiConnectorRequestBuilder.BuildPagingRequest(ConnectorRequestContext requestContext, String location)
   at Microsoft.Flow.RPA.Desktop.Robin.Engine.Execution.Connectors.CloudConnectorRequestHandler.<HandlePagingResponse>d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Flow.RPA.Desktop.Robin.Engine.Execution.Connectors.CloudConnectorRequestHandler.<ExecuteHttpRequest>d__21.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Flow.RPA.Desktop.Robin.Engine.Execution.Connectors.CloudConnectorRequestHandler.<Execute>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Flow.RPA.Desktop.Robin.Engine.Execution.Connectors.CloudConnectorRunner.<>c__DisplayClass34_1.<Run>b__1>d.MoveNext()

排查与解决建议 #

• 检查分页配置：错误堆栈指向分页请求构建逻辑，确认Get Emails V3的分页参数是否配置正确，避免因分页开关开启但未指定合法路径导致空URI请求
• 重新授权邮件连接器：尽管发送邮件正常，但读取邮件的权限可能存在隐性变更，重新完成连接器授权流程，确认包含邮件读取权限
• 验证筛选条件变量：检查Get Emails V3中使用的动态筛选变量（如日期、文件夹路径）是否为空，空变量会导致请求URI构造失败
• 切换连接器版本：尝试使用Get Emails V2版本替代V3，验证是否为版本特定BUG导致的问题
• 更新Power Automate Desktop客户端：确保客户端为最新版本，旧版本可能存在连接器URI处理的已知缺陷

内容的提问来源于stack exchange，提问作者Madhulika Gupta