Drıftstack docs
Docs

‘Some information was not accepted’ (400 validation)

You might be here because: “Some information was not accepted. Check your input and try again.” · “Some information was not accepted: name. Check it and try again.” · “One or more fields failed validation” · “400 bad request” · “validation-failed” · “it won’t let me save the profile” · “the form says something is wrong but not what” · “The request could not be completed. Check your input and try again.”

Short answer

The server checked what you sent and at least one field did not fit — wrong shape, out of range, or a value this server does not know — so nothing was saved or started. Where the server named the field, the app names it too: “Some information was not accepted: model. Check it and try again.” Fix that field and send again.

Check first

  • Is a field named after the colon? Up to three field names are shown, exactly as the API calls them.
  • Did you paste something with extra spaces, a line break, or the wrong kind of value — letters where a number goes?
  • Is the app up to date? A choice the server no longer knows, such as a device or model name, is refused this way, and the field’s name is the clue.

Likely causes and fixes

  1. A named field. Open the form, correct that field, save again. The app never shows the server’s own explanation, only the field’s name.
  2. No field named. The refusal was a general bad-request — the request as a whole was malformed — or the field’s name was not one the app is willing to show. Re-enter the form from scratch rather than editing in place.
  3. From the API or an SDK. A 400 is validation-failed with “One or more fields failed validation.” and an issues object listing each field, or bad-request with a detail. Neither is retryable as sent; read issues, fix, resend.
  4. “The request could not be completed. Check your input and try again.” The app’s fallback for a refusal it cannot classify. Try once more; if it repeats, treat it as a 400.
  5. An older app against a newer server, or the reverse. A value one side knows and the other does not is refused as validation. Update the app from Settings → Check for updates; on a self-hosted server, update the server and app together.

If it still fails

Press Talk to a person in this chat (or open Help) and include: what you were saving or starting, the exact sentence including any field names, the app version, and for the API the issues object from the response. Never include passwords or proxy credentials in the message.