Need help with troubleshooting flow issue and help deciphering detailed log files

[commalliance]

Hi there, so I have been working and improving this flow that I am having a weird issue with, which was just brought to my attention.

So the flow basically is just uploading a file from a networked folder, to our document management systems website, and then moving that file from that networked folder, to an 'processed' network share, only after the upload is successful.

The issue that is going on right now is that even though the flow completes successfully, when I check that record the file is not there.  I have also asked our systems vendor to see if they could help to see if there were any errors, or could see if the files were truly uploaded.  So far that have not seen any errors.

On Friday I changed the log file that's created to be more detailed to include: the folder, the file name, and the date and time it was "uploaded", and our flow ran yesterday, and so today I spot checked the files in the log file, however, after spot checking, I checked all 45 records, and none of them are showing in the system. 

When the flow runs the uploading part, these are the steps:

1. clicks the 'upload' button on the site

2. clicks on the 'browse file' button on the pop-up window

3. Explorer window opens, the flow then inserts the complete path and file name, then clicks open

4. website window processes uploaded file, and then clicks the 'save' button

4. website pop-up window appears stating "upload successful", then flow clicks the 'ok' button to close that window

Then before it processes the next file, if there is another file, you will see the file listed on the website that was just uploaded (when running the flow manually of course.

I am not sure how this flow can succeed, however no file appears, but in prior tests, the flow had an issue with clicking on that last "ok" button, which caused the flow to fail.

Any advise on how to troubleshoot this issue, because EVERY time that the flow is ran manually, from the unattended host, it works, and can verify the file appears on our site, and like I said, the flow ran yesterday successfully (screenshot below) because I am perplexed by this "issue."

I am taking screenshots of the flow steps for you to look at, and I really appreciate your help.

 

[ryule]

For issues like this, I would definitely recommended adding screenshots into your bot, and somehow make the file for each screenshot unique to each report, that way you capture your full history, instead of the screenshot getting overwritten for each file it attempts. I do something like this below, so maybe you could use the variable NoteNumber from your bot or something else you could use that would work as part of a file name:

This way you can see exactly what the bot sees at certain moments in your bot, and it can help you determine how to adjust your bot to determine if a file was successful or not. Perhaps you'll notice you need longer wait times or something else!

[momlo]

Hi @commalliance 

First thing I would check:

You have bunch of action with On Error set up on action level - i suspect your flow might be failing on one of these actions but proceeds to next, as perhaps you are telling you flow to ignore errors on these actions.

Just guessing though.

I would go away from On Error on action level and would use On Error on entire block under loop - this will allow you see what action is failing for a particular file, still you can build logic that will not break the entire flow but go to next file.

Below suggest that perhaps the default (720p) resolution of unattended flow is preventing some of the elements to appear and be controlled by PAD. So i would run it in attended but in 720p to see if that is the case, and then change the UIFlow settings on machine so unattended run 1080p for example.

because EVERY time that the flow is ran manually, from the unattended host, it works,

[commalliance]

@momlo

thanks for the info, but the only steps that I have to move on, if error occurs in my sub flow, which is basically just selecting each drop down option if it exists.  this is done so it can populate all of the tabs on the website, which for our older records, wasn't done automatically.

Also with the resolution, I ran into an issue previously, so I had already changed the resolution in the file which corrected the issue of the unattended flows failing.

I think I found the issue, but was wondering why that the flow wouldn't error out.

So for step 33 clicking on the button to open up file explorer window to browse, when hovering over the web ui element, the outline for that element goes all of the way off the little window, and running the flow step by step, i see the mouse moving to the upper right-hand corner of where the element tag showed.  but I'm perplexed because this is how that portion of the flow has been setup from the start, so why would it all of a sudden fail??

[commalliance]

So, I looked again at the config file to see it the resolution was still set to 1920 x 1280, which it was.  So then I added a step to get the screen resolution and record it in the log file.  When I ran it unattended, the log file said it was running at 1024 x 738.  So I thought that was odd, so I tried adding another step to set the screen resolution to 1920 x 1280, saved the flow, signed out of my desktop, and then manually ran the flow, still no change in resolution.  So then I tried switching the config file back to 1024 x 738 and the rebooted, then changed it back to 1920 x 1280, rebooted again, then ran the flow, but still said it was running at 1024 x 738.

any ideas on why it’s not running in the resolution I set the config file to?

[momlo]

I think some other people reported the same, seems this is a bug

[commalliance]

I see all these threads saying that this should work, so its strange.

[commalliance · Accepted solution]

Well the short term fix to my problem was to change the click steps to conform to the 1024 x 768 resolution, and then the flow ran perfectly,