Mintplex-Labs/anything-llm · error
No updates provided
Error message
No updates provided
What it means
Validation in POST /system/user: after building the updates object from optional username/password/bio fields, it is empty, meaning the request body supplied no changes (or username equaled the current name and password/bio were absent). The update is skipped with a 400 response.
Source
Thrown at server/endpoints/system.js:1273
const id = Number(sessionUser.id);
if (!id) {
response.status(400).json({ success: false, error: "Invalid user ID" });
return;
}
const updates = {};
// If the username is being changed, validate it.
// Otherwise, do not attempt to validate it to allow existing users to keep their username if not changing it.
if (username !== sessionUser.username)
updates.username = User.validations.username(String(username));
if (password) updates.password = String(password);
if (bio) updates.bio = String(bio);
if (Object.keys(updates).length === 0) {
response
.status(400)
.json({ success: false, error: "No updates provided" });
return;
}
const { success, error } = await User.update(id, updates);
response.status(200).json({ success, error });
} catch (e) {
console.error(e);
response
.status(500)
.json({ success: false, error: e.message || "Internal server error" });
}
});
app.get(
"/system/slash-command-presets",
[validatedRequest, flexUserRoleValid([ROLES.all])],
async (request, response) => {
try {View on GitHub (pinned to 20f6d3546c)
Solutions
- Include at least one field to update in the request body.
- Check the payload was serialized correctly.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at server/endpoints/system.js:1259 when the library encounters an invalid state.
Common situations: A user update request arrived with an empty update payload.
AI-assisted analysis of Mintplex-Labs/anything-llm@20f6d3546c (2026-08-18).
Data as JSON: /api/errors/4090d0e5e2ded49f.
Report an issue: GitHub.