Custom-vision training iteration JavaScript export

[YoussefSbeiti]

• Package Name: @azure/cognitiveservices-customvision-training
• Package Version: 5.1.1
• Operating system: Windows 10
• nodejs
  • version:
• browser
  • name/version:
• typescript
  • version:
• Is the bug related to documentation in
  • README.md
  • source code documentation
  • SDK API docs on https://docs.microsoft.com

Describe the bug
When trying to send a second exportIteration() request through the SDK I get the following error:
restError.ts:19 Uncaught Error: {iterationId} is already queued for export

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @areddish, @tburns10.

[ramya-rao-a]

Thanks for reporting @YoussefSbeiti

@areddish, @tburns10, Can you clarify if this is expected behavior?

cc @sarangan12 in case the service team needs any follow up from the client side

[areddish]

@ramya-rao-a Yes, this is expected behavior.

@YoussefSbeiti exporting an iteration is an asynchronous process, you are getting this error because exportIteration was already called on the iteration and it's still queue'd or currently in the process of being exported. We don't allow multiple exports of the same iteration to happen in parallel, you have to wait for the currently queue'd export to finish.

You can get the status of the exports for that specific iteration by calling getExports with the project id and iteration id you are interested in. One of the fields returned will be status and that contains information to let you know if the export is queued, completed, failed, etc.

[YoussefSbeiti]

Thank you for the reply @areddish @ramya-rao-a .
I still get the same Uncaught Error even though the status of the previous request is "Done"

[andreasbotsikas]

Even with python SDK, if you try to export an iteration which has already been exported ("Done" in the list) we get the same error:

{iterationId} is already queued for export

A different error should be emitted to be able to distinguish that the model is already available in the exported list.
FYI @OlivelliAri

[areddish]

Thanks - yes, this is an error in the error message that get's generated. I've logged an issue in our internal task system to provide a better error message and will address in a future roll out.

[ramya-rao-a]

I've logged an issue in our internal task system to provide a better error message and will address in a future roll out.

Hey @areddish,

This package had an update in Nov 2020 with the changes from #12427. Did we get the error message updated as part of this release?

[agribot2]

Please provide a fix for this defect. I do believe it is only a problem with the error message wording. I believe that there is also a functional ( code ) defect that is causing the system to invoke an error message.

[sarangan12]

@areddish Do we have an update on this issue?

[github-actions]

Hi @YoussefSbeiti, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.