Skip to main content
We’re sorry you’re experiencing an error. Here are some troubleshooting steps:
  • Refresh the page: Sometimes a simple refresh can fix temporary glitches.
  • Navigate to a different page: This can help if the issue is specific to the current page.
  • Log out and log back in: Occasionally, a fresh session can resolve unexpected errors.
  • Check variable names: Ensure that all variable names used in your code match the expected keys in the JSON object.
  • Verify path parameters: Make sure the path parameters in your API request are correct and correspond to the expected values.
  • Inspect query parameters: Verify that any query parameters included in your request are accurate and match the expected format.
  • Review body variables: Ensure that the data sent in the request body is formatted correctly and includes all required fields.
The conflict arises because the /student/{id}/ endpoint uses a dynamic path parameter :id, which can potentially match the /bulk segment in the /student/bulk/ endpoint. To avoid this conflict, you can modify the URL paths to be more distinct:
  • /student/{id}/ remains unchanged.
  • /students/bulk/ is a more specific path for bulk update operations.
By using the plural form students in the bulk update path, you clearly differentiate it from the single-item update path.
The forloop.val variable is specific to the loop block and cannot be directly accessed outside of it. Attempting to access forloop.val outside the loop will result in an error indicating that the variable is not in memory.
Yes, the AI Schema Builder is designed to handle complex database schemas with multiple tables and fields.
When using comparison operators (e.g., >, <, >=, <=), verify that the field data types are compatible. For example, If the id field is of type string, using id > 10 would result in an error. You cannot directly compare a string value with a numeric value using numerical comparison operators.