Diagnose a workflow's HTTP lane
writ_diagnose_http_workflowDiagnoses HTTP-lane readiness for a saved workflow. Reports browser-only dependencies, invalid flow actions/expressions, unsafe internal query parameters, eligibility versus actual proof, and the next repair action. task_id (a representative run) confirms whether it really used engine=http, did not fall back, and returned records (an answer such as {ok:true,count:0,listings:[]} is not proof). With task_id it also returns the run's steps and, for a flow, what every request it made was answered with (status, sizes, a response sample): the first evidence when a run returned nothing or failed. A 200 with an empty feed means the site stopped serving this session (signed out, blocked, or a null written over a working request variable), not 'no matches'.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task_id | No | Optional run to verify actual HTTP execution and output. | |
| workflow | No | ||
| workflow_id | No |