One Line Framework: Better Global Error Handling

Hi, I would like to have a recommendation for a better framework for our project.

Below is the project flowchart:

Problem statement: As for now, the whole process is not iterative (one line process) due to suspension at the Action Center. We trigger, from Orchestrator, a new job every minute so that the robot won’t stop process another transaction and will continue suspended process when the Action Center users completed their Action Task (iterative process would hold the process). However, this will slightly affect the continuity of the process as it needs to restart from the beginning for every transaction.

Requirement:

  1. Config file is only read one time for all transactions
  2. Global error handler for all transactions (such as server down, the suspended process won’t be processed yet)
  3. (Might be) Iterative instead of one line

I just would like an opinion to improvise the current framework. Thanks

Hello @azeem_rosli!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly
Forum_Staff