# IFS Cloud: Unable to Save, Internal Server Error and Quick Report Problems > Source: https://netray.co/erp-help/ifs-cloud-unable-to-save-internal-server-error-quick-report > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer In IFS Cloud a save failure or internal server error is almost always a server-side exception returned through the projection the page calls. Read the error detail, reproduce it in the browser network tab, then check the middleware and database logs for the real cause, which is typically a business rule, a missing permission, a bad customization or a stale cache. Quick Report problems are usually a missing permission grant or mismatched bind parameters. ## Kind error ## System ifs ## Erp IFS Cloud ## Module Aurena client / Quick Reports ## Query ifs cloud unable to save element ## Alternate Queries - ifs cloud internal server error - ifs cloud quick report parameters - ifs cloud quick report permission ## Applies To IFS Cloud (Aurena web client), 21R1 and later. Menu names vary a little between releases, so confirm against your documentation. ## Steps ### How to troubleshoot a save or internal server error **Items:** - Read the whole message. Aurena error dialogs often hold the useful text (a business rule, a missing value, a locked record) behind a details link. - Open the browser developer tools, Network tab, repeat the save and inspect the failed request. The response body from the projection call usually has the specific error code and text. - Check whether it is data or system: try the same action on another record and as another user. A failure only for one user points to permissions. - Look at the server side: the middleware application logs and the database error trace for the timestamp of the failure. Internal server errors that have no business message are logged there. - Review recent changes: a custom field, event action, custom logic, a transferred configuration or a service update that landed shortly before the problem began. - If it is a Quick Report, confirm the report is granted to the user and that every parameter in the query is defined and supplied. - If the cause is not clear, collect the request, response, timestamp and user and open a support case with IFS or your partner. ## Sections ### What an internal server error actually means **Body:** Internal server error is the generic envelope for an unhandled server exception. The client cannot tell what went wrong, so the message is vague by design. The detail lives in the response of the underlying projection call and in the server logs. Treat the dialog as a pointer and not as the diagnosis. Frequent real causes are a database constraint or trigger, an unhandled condition in custom logic, a mandatory value that the page did not send, a record locked by another session, a background process still running, or a deployment that has not finished refreshing. Repeat the action with logging on and compare against a working record. ### Quick Report parameters **Body:** A Quick Report is a stored query that a user can run and export from the client. Parameters are values the query asks for at run time. When a report fails or returns no data, first compare the parameters the SQL declares against the ones the report definition lists. A parameter that is present in the SQL but missing from the definition, or a data type mismatch such as a text value compared to a date, gives errors or empty output. Test the SQL on its own in a database tool with the same values, then add it back. Keep the query read-only and filter by indexed columns so the report does not hold locks or time out on large tables. ### Quick Report permissions **Body:** Running a Quick Report needs two things: permission to use the Quick Report feature and access to the data the query reads. A user can be allowed to run the report and still see an error or no rows because the underlying views are not granted to their permission sets. Check the report's own permission assignment, then the user's permission sets, then the database objects used by the SQL. Grant access through permission sets rather than to individual users, so the setting survives staff changes and can be moved between environments with your configuration process. ## Pitfalls - Retrying the save repeatedly instead of capturing the response from the failed request. - Assuming it is a bug when a customization or event action is the cause. - Granting a user the Quick Report right but not the underlying data access. - Writing Quick Report SQL that reads tables directly instead of the supported views. - Changing settings in production without exporting the configuration first. ## Ai Angle An on-prem assistant grounded in your IFS environment can take a pasted error, the request and the log lines, and help match them to known causes in your own configuration: custom logic, event actions and permission sets. Because it runs inside your network on an open-weight model, logs containing customer and part data never leave it, and it only reads. It supports the support engineer, it does not replace IFS support. ## Faq ### Where do I find the real error behind an IFS Cloud internal server error? **Answer:** In the failed network call in the browser developer tools and in the middleware and database logs on the server. The dialog shown to the user is only a summary. Your IFS administrator or hosting partner needs log access to confirm the cause. ### Why can one user save a record and another cannot? **Answer:** Different permission sets, different company or site access, or personal values such as defaults can all change the outcome. Compare the two users' permission sets and test the same record with both. ### Why does my Quick Report return nothing? **Answer:** Typical reasons are a parameter value that matches no rows, a date or text type mismatch, or missing access to the underlying views. Run the SQL directly with the same parameters to see which applies. ### What is IFS Cloud Cable Car? **Answer:** It is not a standard IFS Cloud feature name that we can document. It may be a customer or partner project, a demo or a custom solution name, so ask whoever supplied the term or check your IFS documentation for the exact reference. ## Search terms ifs cloud unable to save, ifs cloud internal server error, ifs cloud error troubleshooting, ifs cloud quick report parameters, ifs cloud quick report permission, ifs aurena error, ifs cloud save failed, ifs cloud logs --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json