I’d look at account-level stuff next, because @reveurdenuit already covered the obvious config rabbit holes pretty well.
What I’d check in Luredai:
-
Workspace or org limits
Sometimes your personal account works, but the team workspace has usage caps, disabled features, or restricted models. -
Billing state
Not just “is payment active,” but whether a trial expired, credits hit zero, or a spend cap got enforced. -
Region/browser mismatch
I actually do think browser matters more than some people say, especially if Luredai uses cookies, popups, or third-party auth. Try private window first before a full cache purge. -
Input formatting
Hidden characters, giant pasted prompts, weird markdown tables, or unsupported file encoding can break runs without giving a clear error. -
Status/history
Check whether older runs still work. If old workflows fail too, that points to platform/account issues. If only the new one fails, it’s your setup.
Pros of Luredai: usually flexible, quick to test ideas, decent model/options workflow.
Cons of Luredai: vague error messages, settings can interact in annoying ways, and team permission issues can look like bugs.
If you post:
- exact error text
- what you clicked right before it failed
- whether it happens on all projects or one
…people can narrow it down fast.