Synapse throws 'CONCURRENT_UPDATE' update error without describing root cause

Description

In web client and synapser, any fileview update in which the etags are out of date results in the 'CONCURRENT_UPDATE' error, but does not guide user about how to fix. This same error can be thrown when there actually is a concurrent update as well. Can we improve the error handling?

Environment

None

Assignee

Unassigned

Reporter

Sara Gosline

Labels

None

Validator

Bruce Hoff

Development Area

None

Release Version History

None

Components

Priority

Major
Configure