ArcGIS Pro 2.6.8; File geodatabase and Oracle 18c 10.7.1 EGDB (versioned - move edits to base):
This is a heads-up to anyone still using Pro 2.6 (or a similar version):
I noticed what seems to be a serious bug in ArcGIS Pro 2.6.8:
If I try to close ArcGIS Pro with unsaved edits, and choose to save edits when prompted, then the edits don’t actually get saved.
- Clicking yes/no/cancel in the subsequent save Pro project dialog doesn’t help; the edits get discarded regardless.
- I think the workaround is to save manually before closing ArcGIS Pro, which is a good practice anyway.
- If you happen to accidently try to close Pro with unsaved edits, then I would suggest clicking CANCEL, not YES, in the save edits dialog.

- And then manually save your edits.
That’s pretty concerning behavior. But it seems to have been fixed in modern versions of Pro, such as Pro 3.2.2/FGDB.
I don't control the version of Pro my organization uses (2.6.8).