Bot Runs Extremely Slow on One XAML After Republish – Need Help

Hi Community,

I have an automation built in UiPath that has been running fine for over a year. Recently, I made some process changes and republished the project multiple times. The package is now at version 1.74, but when I tried to publish again, the process took unusually long. Thinking there was an error, I stopped the publish midway.

When I attempted to republish after that, the package version skipped directly to 1.76 (instead of 1.75). Since then, the bot has become extremely slow on one specific XAML— but the rest of the process runs at normal speed.

Here’s the scenario:

The slowdown happens only on the “Xero Practice Manager” – Create New Job page.
On this page, I have 6–7 activities (Click, Select Item, Type Into).
Normally, it takes 2–3 minutes to process a transaction. Now, it takes 7–8 minutes just for this one page, and overall 10–12 minutes for the entire transaction.
Before and after this page, the bot works fine.

What I have tried so far:

  1. Isolated the XAML – When I take this XAML out of the main project and run it separately, it runs at normal speed.
  2. Recreated the XAML inside the main project – Still slow.
  3. Created a fresh XAML outside the main project and pasted it back – Still slow once inside the project.
  4. Created a separate process for this XAML and linked it back to the main process – Still slow.
  5. Cleaned the project – Removed unused variables, deleted unused XAMLs, and even created a separate library to test. No improvement.

Bot run modes tested: Attended, Unattended, Debug – all show the same slowdown on this page.

Has anyone faced a similar situation where only one page becomes slow after a republish, especially with Xero Practice Manager? Could this be related to project settings, package corruption, or UI Automation descriptors? I’m looking for a foolproof fix so the process returns to normal speed.

1 Like

@projectrpa in your older version do you have the same xaml? If that wasnt a part of your process change. you can try using that to test and check do you see any improvement what i suspect is it could be due to cv selectors also do you see any warn/trace log messages?

@projectrpa,

Use Profile Execution feature available in Studio-> Debug menu.

This will give you activity level time taken. Find the paining activity and look around it.

image

4 Likes