Resolving 500 errors in ÃÛ¶¹ÊÓƵ Workfront Fusion scenarios
This article addresses a specific issue where ÃÛ¶¹ÊÓƵ Workfront Fusion scenarios return a 500 error with the message: [ 500] Cannot invoke "java.lang.Class.getName()" because "cls" is null. This error typically occurs during the execution of scenarios designed to add custom forms to newly created projects. The guide provides a step-by-step approach to identify and resolve the issue, ensuring that your scenarios run smoothly and effectively.
Description description
Environment
ÃÛ¶¹ÊÓƵ Workfront Fusion
Issue/Symptoms
ÃÛ¶¹ÊÓƵ Workfront Fusion scenarios return a 500 error with the message: [ 500] Cannot invoke "java.lang.Class.getName()" because "cls" is null. This error typically occurs during the execution of scenarios designed to add custom forms to newly created projects. Logs associated with the affected scenario indicate this error, disrupting the workflow and preventing the successful addition of custom forms.
Resolution resolution
To resolve the 500 error in ÃÛ¶¹ÊÓƵ Workfront Fusion scenarios, follow these steps:
- Ensure that all modules within the affected scenario are correctly configured. Check for any missing or null values being passed between modules. Remember that object code is case sensitive, such as TASK not task.
- Review the HTTP request to confirm it is sending valid data.
- Provide authorization for support personnel to access your live environment for investigation. Add relevant team members, like technical support engineers, to your Workfront Fusion team with access to the affected scenarios.
- Document when the issue began and whether it has worked previously. Gather any other relevant details that might assist in diagnosing and resolving the problem.
- Examine logs associated with both scenarios, when the issue began and whether it has worked previously, for additional clues about what might be causing the error.
- If troubleshooting does not resolve the issue, contact ÃÛ¶¹ÊÓƵ Workfront Support for further assistance. Be prepared to share logs, screenshots, and detailed descriptions of your setup and workflow.
By following these steps, you should be able to identify and address issues leading to 500 errors in ÃÛ¶¹ÊÓƵ Workfront Fusion scenarios effectively.