willchen96 keeps one shared workflow from taking down the whole backend

When someone shares a saved workflow with colleagues, the project has to look up who shared it before showing the list. willchen96 found that if that lookup went wrong, it didn't just show an error - it could bring down the entire backend. The fix makes the screen fail soft: if a sharer's name or email can't be resolved, the workflow list still loads. It also stops the screen from scanning every account in the system just to identify a handful of sharers, looking up only the ones it actually needs - which trims both errors and running cost as the user base grows.

A second pass tidies how the project talks to its AI engines - Gemini, OpenAI and Anthropic, the large language models behind the product. A missing API key now produces a clear, named error rather than an opaque one.