parag2131 opened a new issue, #37924:
URL: https://github.com/apache/superset/issues/37924

   ### Bug description
   
   Superset Version
   Superset Version: 6.0.0
   OS: Amazon Linux (EC2)
   
   Issue Description
   
   We are getting the following error while saving a dashboard:
   "Your dashboard is too large. Please reduce its size before saving it."
   The dashboard contains multiple KPI Big Number charts and tabs.
   It exceeds the default 65535 JSON size limit.
   
   We updated the backend config:
   DASHBOARD_JSON_MAX_LENGTH = 1000000
   
   The container was restarted after the change.
   However, the dashboard save still fails with the same error.
   
   Actual Behavior
   
   Even after increasing the limit to 1,000,000 and restarting the container, 
Superset still throws:
   "Your dashboard is too large. Please reduce its size before saving it."
   
   Question
   
   Is there another limit introduced in Superset 6.0.0?
   Is this validation happening on frontend?
   Is there a new config key replacing DASHBOARD_JSON_MAX_LENGTH?
   Is there a database-level column limit (e.g., TEXT vs MEDIUMTEXT equivalent)?
   
   <img width="1902" height="929" alt="Image" 
src="https://github.com/user-attachments/assets/8d89c8a1-5430-4b63-a258-fbd33cc8997d";
 />
   
   If there is any additional config required in 6.0.0, please advise.
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [ ] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [ ] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [ ] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to