Bug? When running test task, if payload invalid, doesn't error

[heavy ruin]

I think there was a syntax error in the payload when I was trying to manually run a task via the Test section, but clicking run didn't do anything (no err msg) and I didn't know what was wrong

[next charm]

Hi @heavy ruin. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

The docs don’t mention this specific behavior in the Test UI, so I can’t confirm whether it’s a known bug or just current UX. The “Run tests” page is documented only at a high level (select task, enter payload/metadata, run test), with no detail about how payload validation errors are surfaced in the dashboard. [Run tests]

For payload validation itself:

• If you use schemaTask, invalid payloads will cause errors:
  • Triggering via myTask.trigger(...) validates against the schema and throws if invalid.
  • The payload is also validated before each run; if invalid, the run fails with a TaskPayloadParsedError and skips retrying. [schemaTask]

The docs don’t say how those validation errors appear when you manually run a test from the dashboard, or whether a malformed JSON payload in the Test UI should show an inline error vs. silently doing nothing.

Given that, there are two possibilities:

1. Invalid JSON / syntax in the Test payload UI – behavior is not documented; it may currently fail client‑side without a clear message.
2. Schema validation failure – this should produce a run that fails with a parsing error, but the docs don’t describe how clearly that’s surfaced in the Test page.

Because this isn’t covered in the docs, I can’t say for sure if what you saw is a bug, but it’s definitely worth reporting as a UX issue: the Test page should clearly show when the payload is invalid (either JSON syntax or schema validation) instead of appearing to do nothing.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: