[Bug]: Query execution error: null.

[joincamp]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

From the user perspective, certain basic data queries don't work, and it is confusing as to why. The only user feedback is Query execution error: null.

Diving further in, I can provide further insight and a few things that might need to change. Essentially, the core of the issue is that with the introduction of variables, it encodes all listed variables, including the initial stub variable that hasn't been used.

{
    "path": [],
    "params": [
        {
            "key": "query1.variables.undefined"
        },
        {
            "key": "query1.variables.$queryName",
            "value": "query1"
        }
    ],
    "viewMode": false,
    "applicationId": "...",
    "queryId": "..."
}

This does not show on all data sources, likely because their mappings are hardened against the problem, but I've noticed the error so far on AWS S3 and DynamoDB data sources.

So, these datasources should probably all be able to handle bad user input gracefully (like the REST one does), as well as the UI not trying to encode the placeholder variable.

Expected Behavior

I would expect the UI to only encode "real" variables, and not the placeholder that is there for UX.

The data queries should additionally be able to handle some level of expected input (some work, some don't , which leads to confusion).

Additionally, the logs and stacktrace that come from the error (sorry, I don't have access to the server at the moment) are not very helpful. A user-facing error I understand you may not want to leak details, but I was not able to figure this out without debugging.

Steps to reproduce

• Create a S3 data source.
• Create an app
• create an s3 data query
• configure it with just the bare minimum, such as read all buckets
• run manually, observe error
• configure a button or something to trigger the query and bind the event
• click the button, observe error

Environment

v2.6.3 running on amazonlinux:2023 docker container

Additional Information

No response