Page 1 of 1

What Gets Set In API When Extracting / Completely Idle?

Posted: May 27th, 2010, 7:52 am
by sab12397
When using the XML API via api?mode=queue&start=START&limit=LIMIT&output=xml

I am trying to find out:

1. What gets set when a queue item is being verified/repaired/extracted?
2. What needs to be checked for to ensure that any verified/repairs/extracting has finished?

i.e. top level status is idle/paused but I am unsure if this status can be idle/paused and items can still be verifying/repairing/extracting in the queue?

Thanks

Re: What Gets Set In API When Extracting / Completely Idle?

Posted: May 27th, 2010, 9:49 am
by shypike
Only the history part will tell you, the status should be "Completed" or "Failed".
If a job is in the download queue it isn't finished by definition.

Re: What Gets Set In API When Extracting / Completely Idle?

Posted: May 27th, 2010, 11:42 am
by sab12397
Still referring to "api?mode=queue&start=START&limit=LIMIT&output=xml" - i.e. queue mode API

So does when Idle have jobs finished extracting, verifying and repairing?

Or does (in the same queue mode API output)

Queued

Get set to Queued, Verifying, Repairing, Extracting?

When I was trying to see this it either didn't happen or happen so quickly I did not see it?

Or should I be looking at the History API?

TIA

TIA

Re: What Gets Set In API When Extracting / Completely Idle?

Posted: May 27th, 2010, 2:04 pm
by sab12397
Thanks for help, I think I understand now it looks like the top level status can be idle when it is still extracting and doing other tasks in a slot status.