Preserve Exception Stage Historical Screen Captures

[YasinduDambaden]

Presently we are capable of accessing the screen capture related to the latest exception stage via the control room per RPA Bot.

In a practical environment where the Bot's are executing queue based items, the exception stage is handled. Therefore the bot moves on to the next queue item available. 

When all the items in the queue completes a report is generated to the admin stating the status of each item.

Therefore if more than one queue item raise exception stages, then at the time of inspection by the system admin, only the latest exception stage screen capture per Bot is preserved.

The admin will not be able to have a graphical state of the the system or the environment for the exception stages raised by previous queue items executed by the same bot!

The snapshot of the environment will definitely lead towards quickly identifying the issue a bot is facing in most occasions.

Therefore it will be greatly beneficial to have a way of preserving the exception stage related screen capture per item key (historical screen captures)

[YoannGoudot]

+1 for this request !
We need a way of getting screen capture (screenshots) linked to the Queue items it's related to.
With an historic : even better !

Having them based on the ressource is (for me) unuseable as is.

[ChristopherConr]

I agree that this should be a feature that should be available.  This feature will help out debugging immensely.