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
Currently polyaxon doesn't mark operation as stopped when it cannot find it for whatever reason.
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"operations.core.polyaxon.com \"plx-operation-e38d8ec730424cd28c3941ebbe980b88\" not found","reason":"NotFound","details":{"name":"plx-operation-e38d8ec730424cd28c3941ebbe980b88","group":"core.polyaxon.com","kind":"operations"},"code":404}
Enhancement
I would like that changed so operation is either marked as stopped or not found or whatever when polyaxon can't find it because running state is not factual and it makes integrating polyaxon into workflow unreliable.
The text was updated successfully, but these errors were encountered:
Hi @boniek83 we already have the logic for this in our agent implementation (currently commercial), but not for Polyaxon CE. However we are planning on pushing those changes to CE very soon, we have been working on that for the last couple of weeks, see #1333
boniek83
changed the title
Operation state when it cannot be found
Incorrect operation state when operation cannot be found
Sep 19, 2022
Current behavior
Currently polyaxon doesn't mark operation as stopped when it cannot find it for whatever reason.
Enhancement
I would like that changed so operation is either marked as stopped or not found or whatever when polyaxon can't find it because running state is not factual and it makes integrating polyaxon into workflow unreliable.
The text was updated successfully, but these errors were encountered: