Table Extraction-Activate activities not working after being published to Orchestrator

Help Orchestrator
, , ,
1

I worked on a process that requires data scraping on a site. I have an activate activity to bring the window to the foreground before data scraping.

This works on studio. However, after publishing/deploying to orchestrator, it breaks before getting to the activate activity. I commented that out, so now, it breaks before getting to the use application/browser activity for the data scraping.

PS: It doesn’t throw any package or error, except the exception I placed there to know when the process breaks.

Please I need help with resolving this issue.

2

@DamilolaAdeogun

Is the robot installed in service mode only?

what is the error you are getting?

cheers

3

Hi @Anil_G ,
Thank you for your reply.

Yes, the robot is installed in service mode.

I’m not getting any error. Its just not getting the activate and data scrapping activities part.

The error its throwing is cos of the throw activity I placed there to know when it breaks.

4

@DamilolaAdeogun

If the error is not thrown…then you mean no data is getting scrapped?

Where are you saving the data?

Cheers

5

yes, no data is getting scraped.

I’m saving it in the default variable: ExtractDataTable

I’m really confused on why it’s not working well from Orchestrator.

6

@DamilolaAdeogun

did you do a count?

how did you determine that the data is not extracted?

cheers

7

So it breaks before getting to the table extraction activity

This is a list of the activites it goes through before getting to the table extraction activity

  1. Try-catch 2) Open Browser
    The following inside the open browser
  2. Element exist(for ui automation exceptions) 4) Table extraction

Please see image below

image
image395×742 34.2 KB

8

I’ve been able to make it work with the server being opened, but once I log off the server or minimize the server, it throws an error with same issue of not getting to the extraction point.

I’m not entirely sure of what made it work with the server being opened.

I hope I can get a solution to make the process work seamless without the server being opened.

9

Sign out of the server. Then start the job from Orchestrator. Let Orchestrator open the RDP connection. Don’t connect manually to the machine while the job is running.

10

okay, thank you for your response, I’ll try this also, and share feedback with you!

Thank you

11

@DamilolaAdeogun

Your words confusing…

You are saying there is no error and it completes…but again you are saying it breaks before coming to table extraction…if it is breaking it wuld have thrown an error…are you catching it and throwing aome other error in catch block? If so before theowing log the exception.message and check

Cheers