Skip to content

Hi there are some issues when I am using the hermesswitch and hermes switch ui I will the message which was exaplained to me by hermes switch CLI age... #240

@Interstellar-code

Description

@Interstellar-code

sreeharsha@interstellarconsulting.com added a feedback(#7900635) from http://localhost:3000/chat/20260619_094302_067351
> Hi there are some issues when I am using the hermesswitch and hermes switch ui
>
> I will the message which was exaplained to me by hermes switch CLI agent while trying to understand core reason for error messages. it is as follows,
>
> There's no workflow-engine plugin in the Hermes codebase at all. It was developed as a SwitchUI feature (the code in
> ~/hermes-switchui/src/server/workflow-engine/ and ~/hermes-switchui/src/screens/workflows/) but the backend plugin it calls was never shipped or is from a
> branch that hasn't been merged.
>
> Here's the honest answer:
>
> The workflow-engine plugin doesn't exist. SwitchUI's Workflows and Conductor screens were built expecting a backend plugin (/api/plugins/workflow-engine/*)
> that was never released. The gateway doesn't have that endpoint, and there's no plugin to install for it. The frontend code is ahead of the backend.
>
> My try/catch fix IS the right approach here because:
>
> 1. The plugin literally doesn't exist to install — there's nothing to enable
> 2. The query fires on every page load because useWorkflowDefinitions() is imported in the layouts
> 3. Without the catch, it spams 500 errors into your console on every navigation
> 4. With the catch, it silently returns empty (which is accurate — there are no workflows) and the Workflows/Conductor screens just show "no definitions"
> instead of crashing
>
> The alternative would be to rip out the workflow-engine code entirely from SwitchUI, but that would delete a whole feature section (Workflows screen, Conductor
> screen) that might get a backend plugin in a future update. Silently degrading to empty is the correct graceful handling.
>
> TL;DR: The 500 is a pre-existing bug in SwitchUI — it was written for a backend plugin that hasn't been shipped yet. The try/catch is the right fix until that
> plugin exists. Restart SwitchUI and it'll be clean.

Session details:
- Feedback ID: #7900635
- Browser: Firefox 152.0 (unknown)
- Rating: N/A
- Window Size: 1760 x 683
- Resolution: 1760 x 990
- DPI: 1.09
- Colour Depth: 24-bit
- Category: N/A

Session Replay:
https://app.userback.io/viewer/3431/143039/790063548xpf77w4GX6J6GVcrRfWRWP4mrxV2H7VPg2PR/?sr=1

Console logs:
<br>[vite] css hot updated: /src/styles.css <br>

Events:
<br>ui.click div.root > div.fixed.inset-0.z-[10000].flex.items-start.justify-center.bg-black/45.px-4.pt-[calc(var(--titlebar-h,0px)+1.5rem)].backdrop-blur-sm.sm:items-center.sm:pt-4 > div.w-full.max-w-lg.overflow-hidden.rounded-2xl.shadow-2xl > div.flex.justify-end.border-t.px-5.py-3 > button.rounded-lg.px-4.py-2.text-sm.font-semibold.text-white<br>ui.click main.flex.h-full.flex-1.min-h-0.min-w-0.flex-col.overflow-hidden.transition-[margin-bottom].duration-200 > div.shrink-0.flex.items-center.gap-2.px-4.h-11 > div.shrink-0 > div.flex.items-center.gap-0.5 > button.flex.items-center.justify-center.w-7.h-7.rounded.transition-colors.hover:bg-[var(--m-surface-2,rgba(255,255,255,0.06))]<br>ui.click div.shrink-0.flex.items-center.gap-2.px-4.h-11 > div.shrink-0 > div.flex.items-center.gap-0.5 > button.flex.items-center.justify-center.w-7.h-7.rounded.transition-colors.hover:bg-[var(--m-surface-2,rgba(255,255,255,0.06))] > svg<br>Feedback submitted<br>


---
View feedback details in Userback:
https://app.userback.io/viewer/3431/143039/790063548xpf77w4GX6J6GVcrRfWRWP4mrxV2H7VPg2PR/

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions