Question

BPA Workflow - Async (started by background job) - get notified of errors?

  • 18 January 2024
  • 2 replies
  • 121 views
J
Rank
Userlevel 2
Badge +8

We are trying to use the IFS supplied currency rate downloader BPA workflow as it is described here:

 

 

Finally we could get it to work which is nice.

The normal way it works is in the background initiated by background jobs.

However we cannot find a way to get notified of the errors that occur in the workflow (for instance webservice to download from the currency rates is not accessible).

Background job reaches state ‘Executed’ and does not reflect any error.
How can the user/admin get notified of errors in this kind of asynchronous workflows?

It is Cloud 23.2.0.

2 replies

B
Rank
Userlevel 3
Badge +5

There’s no inbuilt way for workflow to notify async workflow failures. All the async workflow runs are in the table BPA_ASYNC_SYS_TAB with the status. However, you can try something like below.

When you say “webservice to download from the currency rates”, are you using a IFS Rest Call within your workflow. If you do, say your web service is not available. Then in your rest connector, you can get the http error code(you can capture most common error codes starting from 300 using “Add/Modify Response Codes” button in REST Call task). By using a gateway in workflow, based on the status code, you can conditionally write to a table (which you might have to create). That table will serve as a log on failed async workflows. You might be able to further improve by this by feeding data to some sort of email service or something. Just a thought.

J
Rank
Userlevel 2
Badge +8

That is quite sad news for us…

It seems we need to drop the idea of using workflows for the purpose of currency rate updates in the background because it is a must to be able to know whether is was successful or not and also every possible kind error not only the one mentioned above and having extra workaround like logging errors into a some new table sounds really cumbersome.

Actually it is quite strange that this feature is missing (background workflow failure notification in any way to the client) I think it seriously hinders the usability of workflows when it comes to background processing.

Anyway, thanks for info, we are wiser now than before :)

Reply


Terms & ConditionsCookie settings