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 of fractal-server 2.7.0, the response of GET /api/v2/project/{id}/workflow/{id}/ includes additional information.
Now each item in response.task_list has an optional string property warning, which is pre-populated server-side and typically may be one of these:
"Task is not active."
"Current user has no access to this task."
When this warning property is set, we should display it in the task list in the workflow page.
Note that these warnings are blocking: if we try to submit a job which include one these tasks, submission will fail with a 422. If we display the information in advance, it will be more clear for the user.
The text was updated successfully, but these errors were encountered:
I noticed that the endpoint PATCH /api/v2/project/{id}/workflow/{id}/ doesn't return the warning property. Is this expected? Could it be possible to add this property also on that endpoint?
Currently, when the PATCH is called to change the tasks order, the code replaces the displayed tasks list with the patched one and the warning would disappear.
As of fractal-server 2.7.0, the response of
GET /api/v2/project/{id}/workflow/{id}/
includes additional information.Now each item in
response.task_list
has an optional string propertywarning
, which is pre-populated server-side and typically may be one of these:When this
warning
property is set, we should display it in the task list in the workflow page.Note that these warnings are blocking: if we try to submit a job which include one these tasks, submission will fail with a 422. If we display the information in advance, it will be more clear for the user.
The text was updated successfully, but these errors were encountered: