ERROR: root:Missing required field: user_message_content: type

[Treygec]

Hi, I am running into an issue after following all the instructions where I am getting the error in the subject line. I see the request hitting the python server with "INFO: 127.0.01:55464 - 'POST /pipe/stream HTTP/1.1' 200 OK" for each query in OpenWeb-UI, so I know they are communicating. But on the OpenWeb-UI side of things I get the error "Invalid Pipe Body" for all requests"

Any ideas or steps to troubleshoot would be much appreciated. I'm even happy to implement any fix in the code if that ends up being the issue, just would need pointed in the right direct.

[TanGentleman]

Thanks for creating the issue! I'll have to investigate tomorrow, perhaps the schemas have changed over the months, as I haven't actively maintained this portion. Please update if you make any progress on your end!

[Treygec]

Thanks for the quick response. Will let you know if I have any luck but I'm still digging through the code just trying to figure out how it's constructed and don't really know how it fits into Screenpipe requirements just yet. Hoping it's just a small schema tweak like you're saying though!

[TanGentleman]

Bumping this for anyone who has more time that I have this week:

• https://openwebui.com/features/plugin/functions/filter/
• https://openwebui.com/features/plugin/functions/pipe

[Treygec]

Finally got some cycles to dig into this. I have no idea what the pipe body used to be / do but it doesn't map at all to what is being done in core_pipe.py to check for valid body structure from what I can tell. Below is the output I am getting as well as the check being done. Again, maybe I'm doing something wrong, but this seems like a lot of logic to need to change from what I can tell. Also, maybe I'm betraying my own ignorance, but for the life of me I cannot tell where most of this context is coming from, my prompt(s) are showing up in Chat History at the end though.

{'model': 'pipe', 'messages': [{'role': 'user', 'content': '### "
'Task:\nGenerate 1-3 broad tags categorizing the main themes of the chat '
'history, along with 1-3 more specific subtopic tags.\n\n### '
'Guidelines:\n- Start with high-level domains (e.g. Science, Technology, '
'Philosophy, Arts, Politics, Business, Health, Sports, Entertainment, '
'Education)\n- Consider including relevant subfields/subdomains if they are '
'strongly represented throughout the conversation\n- If content is too short '
'(less than 3 messages) or too diverse, use only ["General"]\n- Use the '
"chat\'s primary language; default to English if multilingual\n- Prioritize "
'accuracy over specificity\n\n### Output:\nJSON format: { "tags": ["tag1", '
'"tag2", "tag3"] }\n\n### Chat History:\n<chat_history>\nUSER: explain my '
"last 5 minutes.\nASSISTANT: Failed tool api call.\n</chat_history>'}], "
"'stream': True}")

def is_pipe_body_valid(self, body: dict) -> bool:
"""Validates the structure and types of the pipe body dictionary.

    Args:
        body (dict): The pipe body containing:
            - user_message_content (str, required): User's message text
            - stream (bool, required): Whether to stream the response
            - inlet_error (str, optional): Error from inlet processing
            - search_results (list, required): List of search results
            - search_params (dict, required): Search parameter settings