2 months ago
Issue:
Agent chat fails when message contains special characters (*, $, #, %) with error:
"messages: text content blocks must be non-empty"
Steps to reproduce:
- Send messages like:
hello *How are 5$ credits calculated# test
Observed:
- Message fails with error messages: text content blocks must be non-empty
Expected:
- Special characters should be handled as normal text
Notes:
- Request payload is sent correctly (verified in Network tab)
chatSendMessagemutation succeeds (returns streamId)- Failure likely occurs in downstream processing (content block formatting)
Impact:
Breaks normal chat usage with common characters
Attachments
3 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Thank you for the feedback, I've shared it with the team!
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Update here, this might be related to you having an existing thread with corrupted/empty text blocks in history, failing all future messages. Could you try this in a new chat and see if you run into the issue still?
2 months ago
That might be the cause after sending a message with a special character, all subsequent messages in that chat failed. I didn’t test sending a normal message (without special characters) afterward. My trial just ended, so I can’t re-test in a new chat right now. I normally use Render, and this was my first time using Railway. I reported it after noticing this issue.
Status changed to Awaiting Railway Response Railway • 2 months ago