This error may not necessarily mean that the folder is corrupted. You can try the following steps:
Refresh the Orchestrator page and try adding the asset again.
Check whether you have the required permissions to manage Assets and Solutions in that folder.
Try creating a new test solution and add the same asset to check whether the issue is specific to the solution.
Check if there are any dependencies or naming conflicts with the asset.
Try logging out and back into Automation Cloud, or use an Incognito/InPrivate browser window.
If possible, check the browser console or Orchestrator logs for more details about the unexpected error.
Since you already recreated the asset and the issue persists, testing with a new solution or folder could help identify whether the problem is related to the specific solution configuration.
Could you also share the asset type and any additional error details? This may help identify the root cause.
this usually isn’t related to the folder being corrupted. Try checking whether the asset has any special characters in its name and make sure you have the required permissions on the asset/folder.
You can also try creating a new asset with a different name and type to confirm if the issue is specific to that asset.