Our program at my organization is growing and we are a very mature program. However, sometimes we find ourselves digging into issues that are simple and miss basic troubleshooting in our pursuit to fix things quickly. Does anyone out there have a general activity troubleshooting guide they would like to share? I am looking to create one for my offshore support team and imaging something like the below.
- Issue description
- Activity Properties Checked
- Activity Version - upgrade / downgrade checked
This is helpful and we regularly use these documents as well as the Forum, thank you! My issue is our team is jumping to solutions before really troubleshooting the initial issue. This topic is specifically around activity troubleshooting and best practices for testing an issue. From my experience, it would start with checking the properties and configuration of the activity, testing it against another set of data, etc. This is more basic and less targeted direction. This could very well be too generic and not useful and why I posted here. Thanks for your input!
I understand your concern about your team jumping to solutions before really troubleshooting the initial issue. This is a common problem, and it can lead to a lot of wasted time and effort.
When it comes to activity troubleshooting there are only generic things to be followed rather than a documentation as it keeps varying from project to project
Start by checking the activity properties and configuration. Make sure that all of the required fields are filled in correctly.
Try running the activity with a different set of data. This can help you to determine if the problem is with the activity itself or with the data that you are using.
Debug the workflow to see where the error is occurring. This can help you to narrow down the problem and identify the cause
Search the UiPath documentation and knowledge base for solutions to similar problems.
If you are still having problems, contact UiPath support for assistance.
Remind your team of the importance of testing and debugging.
** * Encourage them to document their troubleshooting steps so that they can learn from their mistakes and help others to resolve similar problems in the future.**
Hope this clarifies
This is what I was thinking also. Thanks!
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.