You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "johannes-ws (via GitHub)" <gi...@apache.org> on 2025/08/12 09:01:21 UTC
[D] Error in sql lab at Superset 5.0.0 [superset]
GitHub user johannes-ws created a discussion: Error in sql lab at Superset 5.0.0
Unable to migrate query editor state to backend. Superset will retry later. Please contact your administrator if this problem persists.
Why is this? @dosu
GitHub link: https://github.com/apache/superset/discussions/34651
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Error in sql lab at Superset 5.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Error in sql lab at Superset 5.0.0
<!-- Answer -->
That error means Superset's frontend tried to save your SQL Lab tab state to the backend (using the `/tabstateview/` API), but the request failed. This migration is controlled by the `SQLLAB_BACKEND_PERSISTENCE` feature flag, which moves query editor state from your browser's local storage to the server database for persistence and sharing across devices.
Common causes include network or backend service issues, misconfigured or missing permissions (like `can_migrate_query` on `TabStateView`), database connection problems, or schema mismatches after upgrades. If your SQL Lab result sets are very large, recent changes in Superset 5.0.0 may also block migration due to new payload size limits (`SQLLAB_PAYLOAD_MAX_MB`) [source](https://github.com/apache/superset/issues/33423#issuecomment-2877450777) [source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/views/sql_lab/views.py).
To troubleshoot: check that your backend services are up, your network is stable, and your Superset instance has the right permissions and database connectivity. If the problem persists, review your Superset backend logs for errors related to `TabStateView` or database commits—these will usually pinpoint the root cause.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=3311b5c8-25a2-4d4f-9b35-ce52a486e9e0) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/34651#discussioncomment-14080444
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Error in sql lab at Superset 5.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Error in sql lab at Superset 5.0.0
<!-- Answer -->
That error means Superset's frontend tried to save your SQL Lab tab state to the backend (using the `/tabstateview/` API), but the request failed. This migration is controlled by the `SQLLAB_BACKEND_PERSISTENCE` feature flag, which moves query editor state from your browser's local storage to the server database for persistence and sharing across devices.
Common causes include network or backend service issues, misconfigured or missing permissions (like `can_migrate_query` on `TabStateView`), database connection problems, or schema mismatches after upgrades. If your SQL Lab result sets are very large, recent changes in Superset 5.0.0 may also block migration due to new payload size limits (`SQLLAB_PAYLOAD_MAX_MB`) [source](https://github.com/apache/superset/issues/33423#issuecomment-2877450777) [source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/views/sql_lab/views.py).
To troubleshoot: check that your backend services are up, your network is stable, and your Superset instance has the right permissions and database connectivity. If the problem persists, review your Superset backend logs for errors related to `TabStateView` or database commits—these will usually pinpoint the root cause.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/3311b5c8-25a2-4d4f-9b35-ce52a486e9e0?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/3311b5c8-25a2-4d4f-9b35-ce52a486e9e0?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/3311b5c8-25a2-4d4f-9b35-ce52a486e9e0?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/3311b5c8-25a2-4d4f-9b35-ce52a486e9e0?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/3311b5c8-25a2-4d4f-9b35-ce52a486e9e0?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/3311b5c8-25a2-4d4f-9b35-ce52a486e9e0?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/3311b5c8-25a2-4d4f-9b35-ce52a486e9e0?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&
nbsp;[](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34651)
GitHub link: https://github.com/apache/superset/discussions/34651#discussioncomment-14080444
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Error in sql lab at Superset 5.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Error in sql lab at Superset 5.0.0
<!-- Answer -->
That error is likely because your connect_args structure is not what Superset or the underlying database driver expects. Instead of nesting your S3 credentials under a config key, you should provide them as top-level key-value pairs inside connect_args. For example, if you're connecting to Athena, it should look like:
```json
{
"engine_params": {
"connect_args": {
"aws_access_key_id": "access",
"aws_secret_access_key": "secret"
}
}
}
```
The exact keys may vary depending on your database and driver, but generally, connect_args should not have a config wrapper—just the credentials directly. If you let me know which database engine you're using, I can give you a more specific example.
For more details, see how Superset expects connect_args to be structured in [the code and docs](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/databases/schemas.py).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=be986274-92e8-4ee2-99a0-9ae4fa4e385b) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/34651#discussioncomment-14080556
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Error in sql lab at Superset 5.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Error in sql lab at Superset 5.0.0
<!-- Answer -->
That error is likely because your connect_args structure is not what Superset or the underlying database driver expects. Instead of nesting your S3 credentials under a config key, you should provide them as top-level key-value pairs inside connect_args. For example, if you're connecting to Athena, it should look like:
```json
{
"engine_params": {
"connect_args": {
"aws_access_key_id": "access",
"aws_secret_access_key": "secret"
}
}
}
```
The exact keys may vary depending on your database and driver, but generally, connect_args should not have a config wrapper—just the credentials directly. If you let me know which database engine you're using, I can give you a more specific example.
For more details, see how Superset expects connect_args to be structured in [the code and docs](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/databases/schemas.py).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/be986274-92e8-4ee2-99a0-9ae4fa4e385b?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/be986274-92e8-4ee2-99a0-9ae4fa4e385b?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/be986274-92e8-4ee2-99a0-9ae4fa4e385b?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/be986274-92e8-4ee2-99a0-9ae4fa4e385b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/be986274-92e8-4ee2-99a0-9ae4fa4e385b?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/be986274-92e8-4ee2-99a0-9ae4fa4e385b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/be986274-92e8-4ee2-99a0-9ae4fa4e385b?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&
nbsp;[](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34651)
GitHub link: https://github.com/apache/superset/discussions/34651#discussioncomment-14080556
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Error in sql lab at Superset 5.0.0 [superset]
Posted by "johannes-ws (via GitHub)" <gi...@apache.org>.
GitHub user johannes-ws added a comment to the discussion: Error in sql lab at Superset 5.0.0
An error occurred while fetching databases: "Connection failed, please check your connection settings"
Why i got this message when try to add engine parameters. This is my connect_args.
{"connect_args":{"config":{"s3_access_key_id":"access","s3_secret_access_key":"secret"}}
@dosu
GitHub link: https://github.com/apache/superset/discussions/34651#discussioncomment-14080492
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org