You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in BSC-ES/autosubmit-api#168, the API will stop deleting the details record when this data is not available (maybe due to deletion, filesystem permissions, etc).
This means that when someone deletes an experiment and then creates another with the same expid, the details of the previous one may be used at least until the API updates it properly when the background task is executed again.
To prevent this, it is ideal to make autosubmit update the details table when an experiment is created (autosubmit expid and autosubmit create) and when it is deleted (autosubmit delete). Note: Not when is archived since we want to preserve the details in that situation.
As mentioned in BSC-ES/autosubmit-api#168, the API will stop deleting the details record when this data is not available (maybe due to deletion, filesystem permissions, etc).
This means that when someone deletes an experiment and then creates another with the same expid, the details of the previous one may be used at least until the API updates it properly when the background task is executed again.
To prevent this, it is ideal to make autosubmit update the details table when an experiment is created (
autosubmit expid
andautosubmit create
) and when it is deleted (autosubmit delete
). Note: Not when is archived since we want to preserve the details in that situation.CC @kinow @dbeltrankyl @mcastril
The text was updated successfully, but these errors were encountered: