I am facing the same problem. I wonder if this affects some users or the whole service?
I am facing the same problem. I wonder if this affects some users or the whole service?






npx wrangler d1 insights <dbname> you can see query timing data)wrangler d1 insights for historical data (like 31 days) will be inaccurate for a bit
npx wrangler@latest d1 insights <dbname> --sortBy reads --timePeriod 7d, will tell you the queries doing this{
"result": null,
"success": false,
"errors": [
{
"code": 7501,
"message": "Internal error: D1 API returned: (400 Bad Request) {\"success\":false,\"errors\":[\"Code: invalid_enum_value ~ Path: action ~ Message: Invalid enum value. Expected 'query' | 'execute' | '_tracing', received 'metadata'\"]}"
}
],
"messages": []
}npx wrangler d1 insights <dbname>wrangler d1 insightsnpx wrangler@latest d1 insights <dbname> --sortBy reads --timePeriod 7d "avgRowsRead": 92284,
"totalRowsRead": 7659605,
"avgRowsWritten": 0,
"totalRowsWritten": 0,
"avgDurationMs": 26.3779313253012,
"totalDurationMs": 2189.3682999999996,
"numberOfTimesRun": 83