In Current exports to BYOD in Azure SQL DB it happens that the export job remains in status executing while export has stopped progress. The reasons might be duplicate key issue which are not reported or it is related to database throttling of Azure SQL DB. The tracking and analysis of such issues is time consuming when no information is presented for the users. In case of data which is consumed for reporting the issue is even worse as partially exported transaction data is used for business decisions.
The Export to BYOD functionality has to report errors and provide enough information to the user to identify the issue.