# ALWAYS get "error during store" when sending - but it succeeds anyway

**URL:** https://discourse.orthanc-server.org/t/always-get-error-during-store-when-sending-but-it-succeeds-anyway/2362
**Category:** Google Groups archive
**Created:** [March 18, 2021, 11:16pm UTC](https://discourse.orthanc-server.org/t/always-get-error-during-store-when-sending-but-it-succeeds-anyway/2362 "2021-03-18T23:16:36Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![ddrucker](https://discourse.orthanc-server.org/letter_avatar_proxy/v4/letter/d/da6949/32.png) [@ddrucker](https://discourse.orthanc-server.org/u/ddrucker)
#### Post date: [March 18, 2021, 11:16pm UTC](https://discourse.orthanc-server.org/t/always-get-error-during-store-when-sending-but-it-succeeds-anyway/2362/1 "2021-03-18T23:16:36Z")

</div>

Every time I use the “send to DICOM modality” button, it sits there for a while saying it’s sending, then says “error during store”.

But if I then go into Jobs, the job is still running - and a few minutes later, succeeds.

Yes, I know about [https://book.orthanc-server.com/faq/improving-interface.html](https://book.orthanc-server.com/faq/improving-interface.html) - but this seems like an actual UI **bug** to me.

What’s more, it’s **trivially** fixed. Instead of blocking here waiting for completion (which could take many many minutes in the case of multi-gigabyte studies), just **have the UI be a link to the Jobs page and a Close button – don’t wait for the job to finish.**

Thanks!  
Daniel

---

<div class="post-metadata">

### Author: ![jodogne](https://discourse.orthanc-server.org/user_avatar/discourse.orthanc-server.org/jodogne/32/1511_2.png) [@jodogne](https://discourse.orthanc-server.org/u/jodogne)
#### Post date: [July 8, 2021, 12:59pm UTC](https://discourse.orthanc-server.org/t/always-get-error-during-store-when-sending-but-it-succeeds-anyway/2362/2 "2021-07-08T12:59:37Z")

</div>

Your suggestion has been implemented by the following changeset:  
[https://hg.orthanc-server.com/orthanc/rev/1a061bc2d6ca](https://hg.orthanc-server.com/orthanc/rev/1a061bc2d6ca)

Regards,  
Sébastien-

---

<div class="post-metadata">

### Author: ![ddrucker](https://discourse.orthanc-server.org/letter_avatar_proxy/v4/letter/d/da6949/32.png) [@ddrucker](https://discourse.orthanc-server.org/u/ddrucker)
#### Post date: [July 8, 2021, 1:16pm UTC](https://discourse.orthanc-server.org/t/always-get-error-during-store-when-sending-but-it-succeeds-anyway/2362/3 "2021-07-08T13:16:19Z")

</div>

Thank you so much!

---

<div class="post-metadata">

### Author: ![ddrucker](https://discourse.orthanc-server.org/letter_avatar_proxy/v4/letter/d/da6949/32.png) [@ddrucker](https://discourse.orthanc-server.org/u/ddrucker)
#### Post date: [December 20, 2021, 1:32pm UTC](https://discourse.orthanc-server.org/t/always-get-error-during-store-when-sending-but-it-succeeds-anyway/2362/4 "2021-12-20T13:32:10Z")

</div>

The “delete” functionality could also use this treatment – Chrome, for example, pops up an “unresponsive page” warning during large deletes. This should also be asynchronous.