Get actual status back of postprocess in the API result #8893
Replies: 7 comments
-
You should use the webroute not the api. The api starts it in a thread. Meaning it will not block other operations. But it means it can't give you a result right away. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Ow yeah. Well we're not changing apiv1 anyway. Soon you don't need to configure pp scripts anyway |
Beta Was this translation helpful? Give feedback.
-
Will v2 work more like Radarr, submit job and then get an ID back you can check the progress on? |
Beta Was this translation helpful? Give feedback.
-
We communicate directly with client on status, progress and ratio. I'll try to remember checking external pre processing scripts |
Beta Was this translation helpful? Give feedback.
-
I'm fine if the API call to import waits till it is finished or if it will do async as long as there is an actual job that I can check if the import has finished in the meantime. With Radarr you can post a job to post process a folder to start the import
That gives back a job with ID that will run async that you can check the progress on
|
Beta Was this translation helpful? Give feedback.
-
We aren't going to invest any more time in the v1 API. We will see what can be done for v2. |
Beta Was this translation helpful? Give feedback.
-
Currently when you call the API with
cmd: postprocess
It will always give
result: success
no matter if the import succeeds.For instance when I call the API on a download it might send back in the DATA
Then somewhere hidden away in
data
it will say: This show isn't in your list, you need to add it before post-processing an episodeCould you also post back the actual result in the API call or give me back a job ID that I can check?
Beta Was this translation helpful? Give feedback.
All reactions