You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @kvistgaard, thanks for reporting this, and sorry it took a while to get to it.
What the message means: "Save as managed query" first sends a SPARQL INSERT DATA to the workspace endpoint and then immediately reads the query back with a SELECT. "Query not found" is raised by that read-back. So the endpoint answered the insert with a success status (otherwise you would see its error message instead), but the triples were not visible to the SELECT that followed.
I couldn't reproduce it: the same save flow works against Virtuoso 7 (open source), both directly and through mathiasvda/simple-cors-proxy, with and without a default graph set on the workspace. So it's most likely something about the specific endpoint setup. Could you help with a few details?
Which store and version is the workspace on (Virtuoso 08.03.3332?), and which URL is set as the workspace endpoint: /sparql directly, /sparql-auth, or through the CORS proxy (http://localhost:8124/proxy/...)? Is authentication configured on the workspace?
Is a default graph set in the workspace settings? If so, which one?
In the browser dev tools Network tab, while saving: the POST whose payload starts with update= and the POST right after it (payload starts with query=). What are their status codes and response bodies?
Right after the alert, what does this return when run directly against the workspace endpoint?
This tells us whether the insert landed in a different graph than the one being read, or did not land at all.
Which browser (Vivaldi, Brave, Firefox?) and which MatGUI version are you on? Does it behave the same in another browser?
Possibly related: you mentioned that managed queries in your SPARQL workspaces disappear repeatedly. If the answer to question 2 is a graph that also gets reloaded or cleared by other processes (a data catalogue graph that is refreshed, for example), that would explain the disappearing queries. A dedicated graph only for the workspace would avoid it.
Activity
MathiasVDA commentedon Oct 19, 2026
Hi @kvistgaard, thanks for reporting this, and sorry it took a while to get to it.
What the message means: "Save as managed query" first sends a SPARQL
INSERT DATAto the workspace endpoint and then immediately reads the query back with aSELECT. "Query not found" is raised by that read-back. So the endpoint answered the insert with a success status (otherwise you would see its error message instead), but the triples were not visible to theSELECTthat followed.I couldn't reproduce it: the same save flow works against Virtuoso 7 (open source), both directly and through
mathiasvda/simple-cors-proxy, with and without a default graph set on the workspace. So it's most likely something about the specific endpoint setup. Could you help with a few details?/sparqldirectly,/sparql-auth, or through the CORS proxy (http://localhost:8124/proxy/...)? Is authentication configured on the workspace?update=and the POST right after it (payload starts withquery=). What are their status codes and response bodies?Possibly related: you mentioned that managed queries in your SPARQL workspaces disappear repeatedly. If the answer to question 2 is a graph that also gets reloaded or cleared by other processes (a data catalogue graph that is refreshed, for example), that would explain the disappearing queries. A dedicated graph only for the workspace would avoid it.
Generated by Claude Code