- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
14-08-20 01:06 AM
We have a action to run macro from BP in excel VBO, the objects waits for macro to complete. If there is any error in macro, it goes into recover. Now when macro runs for long time like 20-30 min, BP is waiting on that action stage, however it crashes the BP and in control room it shows disconnected. Please let us know why this happens and how the same can be fixed?
Ideally BP should be waiting on action stage and whenever macro completes should move to next stage.
------------------------------
Mayank Goyal
------------------------------
Answered! Go to Answer.
Helpful Answers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
25-08-20 01:56 PM
As a test, I created a blank Excel workbook and added the below macro to it. Then I execute it from the VBO and everything worked fine.
Public Declare Function GetTickCount Lib "kernel32.dll" () As Long
Sub WasteTime()
' All this macro will do is run through a loop and then display a dialog.
Dim NowTick As Long
Dim EndTick As Long
Dim Finish As Long
Finish = 10
EndTick = GetTickCount() + (Finish * 1000)
Do
NowTick = GetTickCount()
DoEvents
Loop Until NowTick >= EndTick
MsgBox "We are finished looping!"
End Sub
Cheers,
------------------------------
Eric Wilson
Director, Partner Integrations for Digital Exchange
Blue Prism
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
17-08-20 04:38 AM
If Blue Prism was doing something (Calculating, Logging sessions, etc), it may possible get an out of memory issue during 20-30 minutes time. However, in this scenario, Blue Prism was simply waiting for the completion of the Action stage. I don't see any reason why Blue Prism was crashed. But if Blue Prism does some activities, you can check by enabling "Log Memory Usage" from System > Resources > Management > Right Click the runtime resource > Logging Level. The information will be taken in either
- [BPASessionLog_NonUnicode].[automateworkingset]
- [BPASessionLog_Unicode].[automateworkingset]
Alternatively, you may consider the design change since this is not effective way to use a robot just waiting for another automation has bene done for a long time. Maybe, the process can be divided to 2 parts.
- Do something --> Run the macro --> End
- Pickup the result of the macro --> do the next task --> End
Cheers,
Nobu
------------------------------
Nobuhiro Tokushige
Product Specialist
Blue Prism
Australia/Sydney
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
17-08-20 06:50 PM
On the other hand, you can try creating a very simple macro with a for loop and wait of 1 min in that loop so that it runs for 20 min. Call it in BP process and run process from control room from another machine. I believe you should be able to replicate the issue. It will show disconnected.
Let me know if you were able to find the root cause and a fix.
------------------------------
Mayank Goyal
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
19-08-20 05:02 AM
I crated a sample process based on your information. But the process worked without any issue.
The following image is my process design.
And the following is the screenshot when the process was completed. The runtime resource was still running and I don't see any memory issue.
Just for your reference, I'm sharing my test process and sample excel file. Please find attached files.
Cheers,
Nobu
------------------------------
Nobuhiro Tokushige
Product Specialist
Blue Prism
Australia/Sydney
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
19-08-20 06:24 AM
------------------------------
Mayank Goyal
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
20-08-20 07:15 AM
I modified my process and excel macro running 20 minutes (not 1 minute x 20 by Blue Prism). As a result, Blue Prism could wait for the completion of macro.
I'm sharing the process, excel file and video file of my test. Please run the process and check how it goes in your system environment.
Cheers,
Nobu
------------------------------
Nobuhiro Tokushige
Product Specialist
Blue Prism
Australia/Sydney
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
21-08-20 06:06 AM
The issue is if due to any reason macro got stuck and gives a pop up, BP will stuck for indefinite period of time unless someone goes in and hard kill the process from task manager.
If this action has a timeout option as well we can use the same and if BP doesn't get back control within time out period defined, it goes to exception.
------------------------------
Mayank Goyal
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
21-08-20 02:10 PM
Cheers,
------------------------------
Eric Wilson
Director, Partner Integrations for Digital Exchange
Blue Prism
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
22-08-20 08:38 PM
1) The action run macro with parallel thread is not published, not sure if its ready
2) It is not even mentioned in pdf guide for this VBO
3) I published it on my own and tried using it it gave me an error, please find attached the screenshot
4) How I assume this action is intended to work is - I will have to code a msgbox in my maco at end - something like automation completed, this action will run macro and it waits for that message box. If message box is displayed before timeout, action will click ok on message box and move to next stage else will give exception if no message box is displayed within timeout. Also I am not sure what it will do in case of any internal error within excel macro which shows a error box. How will it differentiate between completion popup and any internal excel error popup?
------------------------------
Mayank Goyal
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
22-08-20 08:42 PM
------------------------------
Mayank Goyal
------------------------------
