Major — a workflow is broken
Likely component: API · Reproducible: Probably
Severity, component, and whether anyone can reproduce it.
Likely component: API · Reproducible: Probably
Severity, component, and whether anyone can reproduce it.
Since upgrading to 4.2.0 the CSV export silently truncates at 1000 rows. No error, no warning — the file just ends. Downgrading to 4.1.7 fixes it. Reproduced on Chrome 141 and Firefox 143 on two different accounts. Steps: open Reports → Export → CSV on any dataset with >1000 rows. Expected all rows, got exactly 1000. This is breaking our month-end close.
The blast radius if this is real.
Where to start looking.
Whether an engineer could hit this today.
Whether it used to work.
Worth checking before opening an engineering ticket.
How much triage work is left to do.
How many users are likely hitting this.
Whether waiting for a fix is the wrong call.
A speculative question, read only when it fires.
Anyone with the link can see it, and it appears in Explore.
POST https://api.typesafe.ai/v1/systemone
{
"state": "Since upgrading to 4.2.0 the CSV export silently truncates at 1000 rows. No error, no warning — the file just ends. Downgrading to 4.1.7 fixes it. Reproduced on Chrome 141 and Firefox 143 on two diff…",
"model": "jev-latest",
"questions": {
"severity": {
"type": "score",
"instructions": "How severe is this issue?",
"criteria": [
"Cosmetic",
"Minor — has a workaround",
"Major — a workflow is broken",
"Critical — core functionality is unusable",
"Catastrophic — data loss or a security hole"
]
},
"component": {
"type": "choice",
"instructions": "Which part of the system is most likely at fault?",
"criteria": {
"Frontend": "UI rendering, client-side state, browser behaviour",
"API": "Server endpoints, request handling, validation",
"Database": "Queries, migrations, data integrity, limits",
"Auth": "Login, sessions, permissions, tokens",
"Infrastructure": "Deploys, networking, timeouts, scaling",
"Integration": "A third-party service or webhook"
}
},
"reproducible": {
"type": "noul",
"instructions": "Could an engineer reproduce this from the report alone?",
"criteria": {
"true": "Steps, environment, and expected-vs-actual are all present",
"false": "Key information is missing"
}
},
"is_regression": {
"type": "noul",
"instructions": "Does this look like a regression — something that used to work?"
},
"is_user_error": {
"type": "noul",
"instructions": "Could this be user error or a misunderstanding rather than a defect?"
},
"report_quality": {
"type": "score",
"instructions": "How good is this bug report?",
"criteria": [
"Unusable — just \"it broke\"",
"Thin — a direction but no specifics",
"Adequate — a clear description",
"Good — steps and environment",
"Exemplary — steps, environment, versions, expected vs actual"
]
},
"blast_radius": {
"type": "score",
"instructions": "How many users does this likely affect?",
"criteria": [
"One specific user",
"A narrow edge case",
"A common configuration",
"Most users",
"Everyone"
]
},
"needs_rollback": {
"type": "noul",
"instructions": "Is rolling back the safer response to this issue?"
},
"security_relevant": {
"type": "noul",
"instructions": "Does this issue have security implications?",
"criteria": {
"true": "It could expose data, escalate privileges, or be exploited",
"false": "A purely functional defect"
}
}
}
}Nine typed answers, one request, about half a second. Pick a lens or write your own questions.