pipeline.start(...) to fire-and-forget an LLM pipeline, then a RunHandler to track it.
You’ll end up with. A task_id / trace_id you can store, plus the eventual result once the run completes — and the pipeline cleaned up afterward.
Expected output
handler.run_status() is non-blocking; handler.result(...) polls until the run finishes (or the timeout trips).
See also
Terminate a run
Cancel a background run mid-flight.
Run pipeline (async)
Same idea, but with
await instead of polling.Pipeline reference
Full method surface.
