frappe-errors-serverscripts

Frappe Server Script sandbox ImportErrors and NameErrors occur when scripts use restricted imports or builtins. You must replace standard imports with safe alternatives like frappe.utils and frappe.parse_json to resolve the sandbox restriction failures.

To fix an empty Frappe API Server Script response, you must explicitly populate frappe.response["message"] with the correct data structure. API scripts require this assignment to return data successfully instead of yielding an empty response.

Frappe Scheduler script changes fail to persist when the script omits the required database commit. You must explicitly call frappe.db.commit in your Scheduler scripts to ensure data modifications are saved to the production database.

You cannot use standard raise statements or try/except blocks inside Frappe Server Scripts due to sandbox restrictions. You must replace raise with frappe.throw to handle exceptions and return errors safely within the execution context.

To prevent SQL injection in Frappe Server Scripts, you must escape any user input affecting SQL conditions using frappe.db.escape(). This security hardening ensures safe query construction and blocks malicious database operations.

Frappe Document Event scripts fail to execute or lack variables when the script type or event is misconfigured. You must verify the Document Event context versus API or Scheduler scripts to ensure the correct variables are available.