Unable to run the job getting error as Faulted it’s stopped running and started displaying an error “faulted” but whenever

Help Orchestrator
,
1

image
Unable to run the job getting error as Faulted it’s stopped running and started displaying an error “faulted” but whenever .

2

Hi!

Your error message indicates that one of your UI-activities could not find it’s selector.

Look at the job’s logs to see if you can establish which one of your activities have failed.
You could run the process in debug-mode locally, or if this is run on a robot you could use remote debugging.

Studio - About Debugging (uipath.com)

3

@Naresh_B_N,

Welcome to the UiPath Community!

It’s expected behavior of the bot job. When a UiPath job is marked as “Faulted,” it means that the execution of the process has encountered an error that prevents it from continuing. Here are some steps to troubleshoot and resolve this issue:

  1. Check Logs: Look into the logs for more details about the error. The logs can provide valuable information about what went wrong during the execution of the job. You can find the logs in the Output panel in UiPath Studio or in the Orchestrator logs if you’re running the job from Orchestrator.
  2. Review Exception Details: If there’s an exception thrown during the execution, review its details to understand the nature of the error. This can help you pinpoint the root cause of the issue.
  3. Debugging: If possible, try running the job in debug mode to step through the process and identify the exact point where the error occurs. This can help in understanding the flow of execution and finding the problematic activity.
  4. Retry Mechanism: Implement a retry mechanism for activities that are prone to transient errors. This can help in making the process more resilient to temporary failures.
  5. Check Dependencies: Ensure that all dependencies required by the process, such as packages, libraries, or external resources, are properly configured and accessible.

In your case bot is clearly failed to Selector issue. Fix it and rerun.

By following these steps, you should be able to diagnose and address the error causing the job to be marked as “Faulted” in UiPath.

Thanks,
Ashok :slight_smile:

4

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.