Visual Builder Workspaces Won't Easily Delete Because VBS Thinks There Are Changes That Have Not Been Committed
(Doc ID 2947686.1)
Last updated on MAY 25, 2023
Applies to:
Visual Builder Studio - Version 23.04.2 and laterInformation in this document applies to any platform.
Symptoms
A Visual Builder Studio Workspace won't easily delete because VBS thinks there are changes that have not been comitted.
After publishing the application, we want to delete the workspace but it says it has files that have been modified.
However, getting the status from the workspace, it says there are no files modified and no changes to commit.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |