I’m trying to run a job that uses the GetProjectMetaData function, but I keep getting an error message saying that the job name doesn’t exist. I’ve double and triple-checked to ensure that I’m referencing the correct name, but I can’t seem to find the issue.
Here’s the relevant section of the code:
GetProjectMetaData('JobName', 'TasksName')
The job name is definitely correct, and I’m running the code from the correct directory. I’m not sure why it’s still throwing an error. I’ve searched through the documentation and Stack Overflow, but I haven’t been able to find a solution.
Additionally, I’m a bit confused about how to properly pass in the ‘TasksName’ parameter. I see that it’s supposed to be a string, but I’m not sure what format it needs to be in. Should it be the exact name of the task, or is there a different format that I need to follow? Any guidance on this issue would be greatly appreciated.
An unhandled exception occurred: job name 'GetProjectMetadata' does not exist
One possible solution to this issue is to check if the job name “GetProjectMetadata” exists in the Orchestrator. If it does not exist, then the exception will be thrown, and the job will not run. The solution is to create the job with the same name in the Orchestrator.
To create a job in the Orchestrator, follow these steps:
1. Open the Orchestrator web application and click on the “Jobs” tab.
2. Click on the “Add Job” button to create a new job.
3. Enter the job name “GetProjectMetadata” and click on the “+ Add” button to create the job.
4. Once the job is created, go back to the UiPath Studio and try running the workflow again.
This solution should fix the issue with the job not running due to the job name not existing in the Orchestrator. By creating the job with the same name in the Orchestrator, it allows the workflow to find the job and run it without throwing an exception.
Hi there! Thanks for reaching out with your question. It seems like you are encountering an “Unhandled Exception” error in your code, specifically, a “Job Name GetProjectMetadata Does Not Exist” error message. While this error may seem confusing at first, it’s important to understand what this error message means in order to properly address it.
Essentially, the error message is indicating that there is a missing or improperly named job in your code. The job in question is “GetProjectMetadata”, which does not exist or is named differently. In other words, the code is attempting to call a job that is not present, resulting in the error message you are seeing.
To fix this issue, you will need to check your code and ensure that the job name is properly defined and spelled correctly. Make sure that the job name matches the name of the job that you want to execute. Additionally, check for any typos or mistakes in the job name that may be causing the error. Once you have identified and corrected any issues related to the job name, the error should be resolved.
If you continue to encounter issues after checking the job name, it may be helpful to review any additional code or dependencies that may be impacting the execution of the job. Make sure to review any error messages or debug information that may be available to help identify the root cause of the issue.
In summary, the “Job Name GetProjectMetadata Does Not Exist” error message is indicating that there is a missing or improperly named job in your code. By carefully reviewing and correcting the job name and any other relevant code or dependencies, you should be able to resolve the issue and get your code running properly again. Good luck!