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
If a dataset fails during copying the data, it has a left over database entry, but it remains "invalid".
However if the execution for that dataset is the default fabricated one, it gets created first, so there will be a left over execution. Should executions then also have a valid/invalid status?
The text was updated successfully, but these errors were encountered:
I think that's the best option.
This is one case where I would consider deleting the execution entry, but that doesn't help - one still has the dataset entry which needs to refer to some execution.
So yes, let's add a status field for executions.
If a dataset fails during copying the data, it has a left over database entry, but it remains "invalid".
However if the execution for that dataset is the default fabricated one, it gets created first, so there will be a left over execution. Should executions then also have a valid/invalid status?
The text was updated successfully, but these errors were encountered: