Skip to content

batch_get_command_status doesn't return stderr when queued offline machine comes back and file does not exist #883

Answered by jsdjjsd
jsdjjsd asked this question in Q&A
Discussion options

You must be logged in to vote

Hi @jshcodes

Thanks for looking into this. I've tested your suggestion now and at first I couldn't get RTR_CheckCommandStatus to return anything useful using the session_id I get per resource from initiating the BatchGetCmd, but it seems that if I use task_id instead I get something useful back, namely that while the endpoint is offline I get complete: False and when it comes back online it returns the stderr I'm looking for. So if I just track the task_id from respective resource I should be fine.

Thanks!

Replies: 4 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by jshcodes
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
RTR Real Time Response issues and questions API usage General API usage issues and questions
2 participants
Converted from issue

This discussion was converted from issue #872 on January 17, 2023 13:45.