Currently, there is no information about a recording until it successfully. A recording may not process for a number of reasons
- a moderator did not click the start/stop record button
- the server ran out of disk space
- there was an error processing the recordings
- a component of the recording was not archived (such as the audio)
We would need to extend the API to return error codes (so the front-end could display the results in appropriate language).
Part of the issues is the BigBlueButton server would not know if the user clicked the start/stop recording button until it was processed. We could mimic the states according to the workflow
At the moment, it not something we've been thinking of doing -- there are a few other items of higher priority on the road map.
Still, we've opened an enhancement request to track it
Regards,... Fred