Unable to Reply in Previous Slack Thread - Need Assistance

Hassan K. · 2026-01-12T17:50:12.600Z

Hey @Anthony P. and 🔒[private user] I've lost the ability to reply on our past thread (https://arize-ai.slack.com/archives/C04R3GXC8HK/p1768156287106929). Are you able to? Is there a different workflow I should use? I mention that because I had a blocker on the next tutorial actually and posted that in GitHub. I don't mind waiting longer on a resolution. I just wanted to check: Is there anything else I should do? I wanted to double-check given that I posted the actual details on the GitHub issue.

Unable to Reply in Previous Slack Thread - Need Assistance | Arize AI Community

6 comments

· Sorted by Oldest

RunLLM
APP
·
·
If you've lost the ability to reply in a Slack thread, it's likely due to channel or thread restrictions, not something you can control. For technical blockers, posting details on GitHub (as you've done) is the correct workflow—maintainers monitor issues there and will respond as able. No further action is needed unless maintainers request more info or clarification on GitHub.If you want to ensure visibility, you can mention relevant team members in the GitHub issue or check for updates periodically. For urgent matters, joining the project's Slack (if available) or using other official support channels is also appropriate, but GitHub remains the main place for technical issue tracking and resolution according to Phoenix contribution guidelines.Would you like more detail on how to follow up or escalate if you don't get a response?Sources: - Phoenix contribution guidelines
💡 Hint: Mention RunLLM in the thread for followups.
👀1
Srilakshmi C.
·
·
hey Hassan K., was looking into that this morning. I’ll do some checking and will respond here when I have an update!
Hassan K.
·
·
Thank you!
Srilakshmi C.
·
·
Hassan K., what endpoint are you using for your project? you may have to update your client code:
from phoenix.client import Client px_client = Client(endpoint="http://your-phoenix-server:6006")
also, the '503 Bad Gateway' message typically means that it might just be a network issue, meaning that the Phoenix server was probably unavailable or not responding to the client request. This is a server-side issue, and may not be a problem with your code syntax. could you try respinning phoenix instance and run these again?
Hassan K.
·
·
Thanks! I'm almost certain I was using the default endpoint and the other tutorial workflow seemed to be working. I'll try that again though and report back.
👍1
Hassan K.
·
·
I wasn't able to get back to this but I'll check the GitHub Issue if I'm able to again sometime. Thanks team!

RunLLM
APP
·
·
If you've lost the ability to reply in a Slack thread, it's likely due to channel or thread restrictions, not something you can control. For technical blockers, posting details on GitHub (as you've done) is the correct workflow—maintainers monitor issues there and will respond as able. No further action is needed unless maintainers request more info or clarification on GitHub.If you want to ensure visibility, you can mention relevant team members in the GitHub issue or check for updates periodically. For urgent matters, joining the project's Slack (if available) or using other official support channels is also appropriate, but GitHub remains the main place for technical issue tracking and resolution according to Phoenix contribution guidelines.Would you like more detail on how to follow up or escalate if you don't get a response?Sources: - Phoenix contribution guidelines
💡 Hint: Mention RunLLM in the thread for followups.
👀1
Srilakshmi C.
·
·
hey Hassan K., was looking into that this morning. I’ll do some checking and will respond here when I have an update!
Hassan K.
·
·
Thank you!
Srilakshmi C.
·
·
Hassan K., what endpoint are you using for your project? you may have to update your client code:
from phoenix.client import Client px_client = Client(endpoint="http://your-phoenix-server:6006")
also, the '503 Bad Gateway' message typically means that it might just be a network issue, meaning that the Phoenix server was probably unavailable or not responding to the client request. This is a server-side issue, and may not be a problem with your code syntax. could you try respinning phoenix instance and run these again?
Hassan K.
·
·
Thanks! I'm almost certain I was using the default endpoint and the other tutorial workflow seemed to be working. I'll try that again though and report back.
👍1
Hassan K.
·
·
I wasn't able to get back to this but I'll check the GitHub Issue if I'm able to again sometime. Thanks team!