Flow failure may be bug?

[alee001]

The flow was normal until yesterday, but it suddenly reported an error this morning. I have tried to restart, but failed four times.

Why does a UI element [click the button in the window] get an error (the window cannot be found) every time it is executed to the 16th time (20 times in total) in the loop?

Finally, it is normal to delete it and re-establish it. This incident has happened for the second time this month, is there a bug?

[Agnius]

While I really doubt it is a bug and is almost certainly an issue with your selector, if you believe it is a bug, I'm quite sure no one will manage to persuade you to change your mind. I have already witnessed that on several of your topics related to this very same process. 

So, if you really believe this is a bug, please simply raise a support ticket with Microsoft. No one on this forum will resolve a bug for you. This is a community forum that can provide solutions to flow-related issues. A bug can only be sumbitted via appropriate support channels. Please do that and have Microsoft support team look into your issue.

[alee001]

Thanks for your advice,

If this is just a problem with a simple selector, it will not just randomly report errors in the loop, and it will not succeed after being repaired today, but fail the next day.

Of course I understand that if it is a bug, the discussion forum is not capable of solving it, but you can also ask questions to attract everyone's attention.

Reporting to Microsoft just wants them to improve, but it does not mean getting their response, because they will just ignore the rare problems.

[Agnius]

It can easily be a selector issue or a bad flow logic issue. I've never had a flow that would run once and then start failing because of a bug. And I've built 100s of projects for dozens of clients. If it runs and then starts failing, it is almost certainly a bad flow logic or a selector issue.

And Microsoft does take their time to look into your issues and suggest solutions. If it is a bug, they will fix it. If it's not a bug (which is very likely), they will look into your flow and tell you how to fix it. 

[alee001]

In the past, the process of running twenty VBA files was to capture all of them buttons, although there were too many steps and the execution time was slow, I never encountered a problem.

After simplifying the process and switching to loop and parameter execution, errors often occur. It is executed four times a day in the morning and evening. The first time is sure to succeed, but every time it is the second or third execution, the same position error occurs and needs to be reset.

Isn’t this a bug?

[Agnius]

No, it is very unlikely to be a bug. If it was a bug with a specific action, you would not get a single successful execution, or it would be completely random.

[alee001]

If it is not a bug, why is there no problem with the settings and parameters of other buttons of the same type, but only this button has a problem?

[Agnius]

That's the exact reason why it is not a bug. A "button" is an element you captured. Not an action in PAD. The action is likely Press button in Window or something like that and the same action does not fail with other elements. If it was a bug with this action, don't you think it would also fail on other buttons, too? 

[alee001]

The following four buttons are all of the same type and settings. How to explain that only the [Capital] button has an error, and the other buttons have no problem?

[Agnius]

It is likely under a different parent window element from the other three. Or it's not there on the screen when the action runs. Again, either a selector issue or a flow issue.

But, for the last time, I'm not here to argue with you or try to persuade you that you're wrong. I've tried that previously and failed. I have already suggested numerous times that if you do not believe me, raise a ticket with MS, so they can look into your issue. Why don't you do that?

[alee001]

Thank you for your response. I am not denying your experience, but some situations cannot be explained and resolved by normal methods.

Suspecting that this is a bug is not just a process or function problem, but also a problem with the background server connection.

When I report this problem to MS, I don't know if they pay attention or improve it.

Below is my complete process to automate the form of twenty VBA files:

[Agnius]

One thing is certain - if you don't report the "bug" to MS, it will definitely not be fixed. If it really is a bug, the ONLY way to fix it is by reporting it.

[alee001]

Although it can't solve the problem, thank you for your attention.

[alee001 · Accepted solution]

Glad to finally find out that the solution is to press the button again on error. (as pictured)