UiPath keeps execution/trigger active even after removing Run Local Triggers

Help Forum
1

Hello, everyone. I’m developing a project in UiPath Studio called CadastroAtendimento03 and I’m facing a problem where UiPath continues to execute/listen for a trigger even after I’ve removed the activities responsible for initializing the triggers.

My project has a form ListaAtendimentos with an event “New appointment clicked”, which triggers the CadastroCliente form.

Initially, in Main.xaml, I had the activity Run Local Triggers, followed by Show Form. After I started having the problem, I disabled these activities in Main.xaml.

Additionally, I:

  • disabled “Continue executing the workflow”;
  • disabled the Run Local Triggers in Main.xaml;
  • disabled the Show Form in Main.xaml;
  • ended the UiPath processes through Task Manager;
  • restarted the computer.

Even so, the behavior continues. The computer exhibits a sort of flickering/reloading of the screen, making it difficult to access the project normally. I have the impression that some UiPath component remains active or that the trigger/form is running in the background.

What’s strange is that the last time, I had enabled the option “Continue executing the workflow” and got the same error. However, I have already disabled it, and the error persists. Additionally, the screen keeps flickering and reloading on the machine too.

Any guidance on how to diagnose this behavior would be greatly appreciated.

2

@CAROLAINE_DA_SILVA_MACHAD

Have you tried restarting the machine once? If not give it a try.

Also try to delete .local folder from the project.

3

Hi @CAROLAINE_DA_SILVA_MACHAD

Since you have already disabled the activities and restarted the machine, please check if any UiPath process is still running in the background.

Also search the entire project for Run Local Triggers and the New appointment clicked event to make sure they are not being initialized elsewhere.

If the screen is still flickering, close UiPath Studio/Assistant completely and end all UiPath processes from Task Manager, then test again.

4

Hi @CAROLAINE_DA_SILVA_MACHAD ,

Try these steps:

  1. Stop all running jobs

    • Close Studio and Assistant completely.
    • End all UiPath.* processes from Task Manager.

  2. Check Local Triggers

    • Open UiPath Assistant → Triggers and make sure no local trigger is enabled.
    • Disable or delete any existing trigger linked to the project.

  3. Clean project cache

    • Delete the project’s .local, bin, and obj folders.
    • Reopen the project and publish/run again.

  4. Check Startup Applications

    • Ensure UiPath Assistant or the project is not configured to start automatically with Windows.

  5. Create a fresh test project

    • Create a new blank project and open it.
    • If the flickering stops, the issue is likely caused by a corrupted trigger configuration in the original project.

  6. Reset trigger configuration

    • Review project settings and any persistence/background execution settings.
    • Remove old trigger definitions and recreate them if needed.

Thanks

5

Hi @CAROLAINE_DA_SILVA_MACHAD,

Since you’ve already disabled the activities/options, killed the UiPath processes and restarted the machine, I wouldn’t keep repeating those steps.

At this point I’d try to identify what is actually initiating the execution.

A few things I’d check:

  1. Check whether the execution is appearing in UiPath Assistant/Robot as a new execution or whether the existing process is simply continuing.

  2. Check Windows Task Scheduler for anything launching the UiPath process/project.

  3. Check UiPath Assistant/Robot logs around the exact time the screen starts flickering.

  4. If the project is connected to Orchestrator, check whether there is an active trigger/job associated with this process.

  5. Temporarily move/rename the project and see whether the behaviour continues.

  6. Check whether another application/process is repeatedly opening or refreshing the form.

The screen flickering/reloading is an important clue. If you can capture the Robot/Assistant log entries from the moment the execution starts again, that should help identify whether the trigger is coming from UiPath itself, Orchestrator, Windows, or another process.

I would first establish the source of the execution before changing anything else in the workflow.

6

@ashokkarale
I’ve already restarted and shut it down, but the problem persists.
I don’t want to delete the folder to avoid losing what I did.

7

@Monali_Vekariya
Thank you, your response helped solve my problem.

8

@Roshan.Manchanayake
Thank you, your response helped solve my problem.

9

@Jasmin_Bar
Thank you, your response helped solve my problem.