Supporting Support (ref#HMLJT0)

What’s happening?

· Something else

How can we help?

· None of the above

Other options

· Other

Describe the issue

I have sent a support request, Roon support emails me that "We've got your technical support request", giving me a request ID and a link. When I click on it, the site shows me a 2022 support thread. No trace of my new support request (???)

Describe your network setup


Replying to myself: Well, at least this thread does appear in the forum.

I can find no trace of it on the forum, I’d recommend resubmitting.

1 Like

Exactly, it’s nowhere. I will try a workaround, creating a placeholder here and then editing it and pasting my support question.

I would first just go through the normal support request process.

Many requests per day are initiated this way without issue.

Update… I see you did it already…

1 Like

Thanks, Carl.

Yes, but only after I tried the normal process four times, all of them unsuccessful. I could not make my content to appear in the forum, and 3 links I received from Roon pointed to other posts of mine. Perhaps it is that I pasted my content in the form from a Word document and there were some formatting issues.

Strangely, the very first message I received was from Roon Community, a bizarre text seemingly generated by an OpenAI API:

" We’re sorry, but your email message to [“”] (titled {“responseText”:{“error”:{“message”:“We could not parse the JSON body of your request. (HINT: This likely means you aren’t using your HTTP library correctly. The OpenAI API expects a JSON payload, but what was sent was not valid JSON. If you have trouble figuring out how to fix this, please contact us through our help center at”,“type”:“invalid_request_error”,“param”:null,“code”:null}},“responseHeader”:{“date”:“Tue, 18 Jun 2024 16:17:14 GMT”,“x-request-id”:“req_6b42be1b7acb930d213e5bb81531b860”,“content-length”:“443”,“set-cookie”:“_cfuvid=ysTBynQfwMfruTJyVSLw8.dmV0SznVI0Qn7isFpfoOs-1718727434745-; path=/;; HttpOnly; Secure; SameSite=None”,“server”:“cloudflare”,“cf-ray”:“895c96a2ab2cc3c6-SEA”,“vary”:“Origin”,“content-type”:“application/json; charset=utf-8”,“connection”:“keep-alive”,“cf-cache-status”:“DYNAMIC”,“alt-svc”:“h3=“:443”; ma=86400”,“strict-transport-security”:“max-age=15724800; includeSubDomains”},“responseCode”:400} (ref#OPCOTA)) didn’t work.


Title has already been used

If you can correct the problem, please try again."