Evane API errors describe different failure classes. The status code is more useful than a generic toast.
The example shows an invalid Participant write rejected by the server and rolled back in the workspace. Request-specific 401, 403, 404, and 422 responses appear in the affected workflow or browser network response rather than on the public system-status page.
401: sign in again
The request has no valid session. Sign in again, then return to the same workspace. If every refresh loses the session, check the frontend/API origin and cookie configuration.
403: access is denied
You are signed in, but your workspace role or an external grant does not allow the operation. Confirm the active workspace and role. Microsoft file and mail actions can also return 403 when delegated consent is missing; reconnect or re-consent from Settings when Evane offers that path.
404: the record is unavailable
The URL or record ID no longer resolves in the active workspace. Refresh the list and open the record again. A SharePoint item can also disappear after it is moved, deleted, or no longer visible to your Microsoft account.
422: the request is invalid
The server rejected one or more fields. Review required values, date formats, IDs, role names, and unsupported extra fields. Correct the form instead of retrying unchanged.
For support, include the endpoint, method, status, error name, and safe request fields. Do not include cookies or tokens.
