Idea Details

Scheduler/Process extended return value

Last activity yesterday
Walter Koller's profile image
By: Walter Koller
11-24-2022 10:23

Currently tasks only provide the status: completed / failed that can be used in Schedules to control the process flow.
Branching the execution path can only be achieved by creating artificial termination / fail status. 

It would be nice if the Scheduler can fetch the process return value (output variable) and then apply simple comparison.



comparison like: =, <, >, <>  
Actually it does not matter. The more flexibility the better but everything is better than having no decisions in Scheduler execution.

Currently there is only 'completed' or 'failed' that can be used for evaluation.
The issue is, artificial 'failed' cannot be distinguished from actual failed executions.
And this is not very 'nice' in a couple of ways:
  • Monitoring SW will count those 'failed' as issues although they might be intentional
  • There is no way to see if there was an actual error during execution (I would not want to check logs every day)
  • The process completes successfully, then it should have status 'completed'. An example: If I want to distinguish two pairs of variables of green & red and 1 & 2. It would be awkward to merge them together to : (green && 1) = green ; !(green && 1) = red

In some cases it might be possible to create another processes that does the evaluation and then starts the other processes as sub-processes instead of them being tasks in a schedule. Unfortunately, those sub-processes are not shown in the Control screen and any errors have to be first investigated instead of being visible at a first glance.
Also having this would not work when login / logoff is involved in the Schedule.


Hi Walter,
Two questions:

  • What sort of comparison do you have in mind?
  • What would this proposal add over the end status and the available log?

Ideas Portal

• Like this idea? Tap the up arrow!  Ideas with over 15 votes will be discussed with our product teams in our idea review meeting.
• Discussion is healthy! If you have a question or comment, don’t be afraid to jump in and start a discussion in the comments section below.
• Collaboration is the key to making magic happen!
This idea is new to the community and hasn’t been reviewed yet. While in the New stage, it is particularly important to vote and comment to further the discussion around this idea.
This idea already exists! A change to the Duplicate status will include a comment linking to the existing idea, so all voting and feedback can be collected in one place.
Need More Info
We’ve reviewed this idea, and determined we need a bit more info before deciding on how to move forward. An update to the Need More Info status will be accompanied by a comment explaining which additional details are needed. Ideas are still open for voting and comments while in the Need More Info stage.
We have all the info we need and are planning to review the idea for implementation feasibility and value added to the product. Ideas with this status are still open to community voting and discussion.
Under Consideration
We have all the info we need and are currently considering the feasibility of implementing this idea. Ideas in the Under Consideration status are still open to community voting and discussion.
Not Planned
We’ve reviewed this idea, and determined that it’s not feasible to implement right now. Ideas in the Not Planned status are no longer open for voting.
We’ve reviewed this idea and have determined that it will be delivered in the near future. Ideas in the Planned status are not attached to a binding timeline, but there is a concrete plan to implement this idea.
We’ve reviewed this idea and confirmed that this is planned for delivery in the next 6 months.
Congrats! Your idea has been accepted by the team and is now delivered! Give yourself a pat on the back – you contributed to the improvement of one of Blue Prism’s products or services!