使用动态发送端口捕获错误 [英] Error capture with dynamic send port
问题描述
我有一个事务类型=无的Ochestration。有一个带有业务流的scope_1（事务类型=无），并且在成功的情况下，我发送了带有处理文件中某些内容的电子邮件通知。
这是业务流程中的一个循环，它基于条件会生成一个或多个连接到动态发送端口的文件。根据条件，设置动态地址并发送文件。
我遇到以下问题。
1。当文件从orchestartion传递到动态发送端口时，如果由于任何原因它在发送端口中失败，我无法在业务流程中捕获它以引发错误。但是，orchestartion中的流程转移到最后一步，即发送成功状态的电子邮件
。所以我收到一封电子邮件通知，说明文件生成等，但它在管理控制台中失败了。
2。当 我试图向scope_1添加一个异常块，它会引发一个错误，说明了系列化错误，为此我最终删除了异常块，因为我试图在excpetion块中捕获错误并发送一封错误$ b $的电子邮件b细节。
Raja
I have an Ochestration with transaction type= None. Have a scope_1(transaction type=none) with business flow and on success, I send out email notification with some contents in the processed file.
The is a loop in orchestration, which based on condition would generate one or multiple files which is connected to a dynamic send port. Based on the condition, the dynamic addresses are set and files are send out.
Am runnning into the following issues.
1. When the file is passed to the dynamic send port from the orchestartion, if it fails in the send port for any reason, I cant capture it in the orchestration to raise an error. But the flow in the orchestartion moves to the last step which is sending
out an email with success status. So I get a email notification stating file is generated etc, but it would have failed in the admin console.
2. When i tried to add a exception block to the scope_1, it throws an error stating serilaization error, for which I ended up removing the exception block, as I was trying to capture error in the excpetion block and send an email with the error
details.
Raja
推荐答案
这应该是一个非常容易解决的问题。
This should be a very easy problem to solve.
在动态发送端口上，将传递通知设置为已传输。
这将阻止发送端口的业务流程直到发送成功（在重试之后）或将错误返回到您可以处理它的业务流程。
That will block the Orchestration at the Send Port until the Send is successful (after any retries) or return the error to the Orchestration where you can handle it.
这篇关于使用动态发送端口捕获错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
