Instance lock management is a little screwy right now. Currently:
widget_instance_lock in the v1 API will lock an instance for a given user for two minutes. widget_instance_lock is called once when the creator first initializes, but never again. The cache item associated with the lock method persists for two minutes, which means after two minutes the instance is again considered editable. Additionally, the creator will enter a failure state if trying to edit an instance locked by someone else, but it's not graceful - the error dialog is blank and it can be dismissed without reloading or exiting the page.
Two improvements to this feature could include:
Ensure the widget_instance_lock request is performed on a two-minute interval while someone is on the creator page (easiest solution might be to set the query's staleTime to two minutes).
Improve creator failure state when the lock request returns false.
Instance lock management is a little screwy right now. Currently:
widget_instance_lockin the v1 API will lock an instance for a given user for two minutes.widget_instance_lockis called once when the creator first initializes, but never again. The cache item associated with the lock method persists for two minutes, which means after two minutes the instance is again considered editable. Additionally, the creator will enter a failure state if trying to edit an instance locked by someone else, but it's not graceful - the error dialog is blank and it can be dismissed without reloading or exiting the page.Two improvements to this feature could include:
widget_instance_lockrequest is performed on a two-minute interval while someone is on the creator page (easiest solution might be to set the query'sstaleTimeto two minutes).