Unable to Retrieve Cached Screenshot from Superset API

[juliacebria]

I am trying to generate and retrieve a dashboard screenshot from Apache Superset using the /cache_dashboard_screenshot/ and /screenshot/{cache_key}/ API endpoints. The request to generate the screenshot returns a 202 Accepted response along with a cache_key, but when attempting to retrieve the screenshot using this cache_key, I receive a 404 Not Found error.
Steps to Reproduce

Send a POST request to:

http://localhost:8088/api/v1/dashboard/2/cache_dashboard_screenshot/

with the following payload:

  {
      "dataMask": {
          "filters": [
              {"col": "name", "op": "IN", "val": ["Aaron"]}
          ]
      }
  }

Response:

{
  "cache_key": "60d0f310ff6af584fd30ea53e217c0d6",
  "dashboard_url": "http://superset:8088/superset/dashboard/p/jJAxQlyLVYm/",
  "image_url": "http://superset:8088/api/v1/dashboard/2/screenshot/60d0f310ff6af584fd30ea53e217c0d6/"
}

Wait for 15 seconds to ensure the screenshot is processed.

Send a GET request to retrieve the screenshot:

http://localhost:8088/api/v1/dashboard/2/screenshot/60d0f310ff6af584fd30ea53e217c0d6/

Response:

    {
      "message": "Not found"
    }

    Status Code: 404 Not Found

Additional Information

Running Superset in a Docker Compose environment.
The issue persists even after waiting longer before retrieving the screenshot.
The dashboard exists.

[dosubot[bot]]

I found some similar discussions that might be relevant to your issue:

1. Unable to get a screenshot of a chart - This discussion is still open and might provide some insights into similar issues with screenshot retrieval ^[1].

2. API /chart/{pk}/cache_screenshot/ - This is another open discussion that could be related to your problem ^[2].

Regarding the 404 Not Found error when retrieving the screenshot, there are a few conditions under which this can occur:

• The chart or dashboard does not exist, which doesn't seem to be the case for you since you mentioned the dashboard exists.
• The screenshot is not found in the cache. This can happen if the cache entry has expired, been invalidated, or if there was an issue during the caching process ^[3].

Additionally, ensure that the necessary feature flags for thumbnails or screenshot endpoints are enabled, as their absence can lead to a 404 status code ^[4]. Also, verify that your caching system is properly configured and enabled, as a missing or misconfigured cache can prevent the screenshot from being stored and retrieved ^[4].

If you haven't already, you might want to check the logs for any errors or warnings related to the screenshot generation and caching process, as they can provide more detailed insights into what might be going wrong ^[4].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}