{"section":"known-issues","requestedLocale":"en","requestedSlug":"giftcard-hub-call-receives-500-error","locale":"en","slug":"giftcard-hub-call-receives-500-error","path":"docs/en/known-issues/Payments/giftcard-hub-call-receives-500-error.md","branch":"main","content":"## Summary\n\n\nWhen the Giftcard Hub receives any error, it ends up returning a **500 error** to the user. This occurs because errors are handled in the Giftcard System code.\n\nThis behavior can happen across different requests, regardless of the HTTP verb. The root cause is that when the Giftcard System does not find content in the response, which is common in **4xx** and **5xx** responses, it clears the content from memory.\nLater, when the code tries to access this element again, it has already been disposed of, resulting in the following error message:\n\n\n    Cannot access a disposed object. Object name: 'System.Net.Http.StreamContent'.\n\n##\nWith this, the user does not have clear information about what happened, which makes troubleshooting much more difficult.\n\n\n#### Simulation\n\n\nIt is not possible to simulate this behavior.\n\n\n#### Workaround\n\n\nNone."}