Labnana List Tasks
Your whole generation history, one page at a time — and how to audit your spend
- client
- tasks_json
- latest_task_id
- total
ComfyUI-Labnana is a pay-per-credit API pack, which means your "generation history" isn't a folder on disk - it's a list on Labnana's servers, and it costs money every time you add to it. LabnanaListTasks is the paged browser for that history: every generation you've submitted, filtered by status, with pagination. It's an output node, so you run it and read the JSON in the UI. The two reasons you'd reach for it: auditing what you've spent, and finding the task_id of an old job you want to fetch or re-use.
How it works
It hits the tasks endpoint and returns the current page of your generation history as pretty-printed JSON. Because task state lives server-side, the node always re-queries on every run rather than trusting ComfyUI's cache.
The inputs are simple:
page(default 1) andpage_size(default 20, max 100) - paging, standard stuff.status_filter-all,pending,generating,success, orfail. Filtering onfailis the fastest way to find the jobs that ate credits without producing an image.
Outputs:
tasks_json(STRING) - the full page of tasks, pretty-printed, with each task's status,failMsgif it failed, and image URLs if it succeeded.latest_task_id(STRING) - the newest task on the current page; handy as a feed into Labnana Get Task if you want the most recent job's images.total(INT) - how many tasks match overall, which tells you whether you're only seeing the first page.
Install
Search Labnana in ComfyUI Manager, or:
cd ComfyUI/custom_nodes
git clone https://github.com/exoticknight/ComfyUI-Labnana.git
Restart. Only dependency is requests, and you need your ls_... key in the Labnana API Client node or the LABNANA_API_KEY environment variable.
Gotchas
- It's read-only, so it costs nothing to run. Unlike the generation nodes, listing your history doesn't spend credits. Fire it up whenever you want.
- The page defaults are small. With
page_size20, a busy account fills pages fast. Bump it toward 100 for a real audit. latest_task_idonly reflects the current page. If you filter tofail, that's the newest failure, not your newest task overall. Keepstatus_filteronallwhen you want the genuinely latest job.- You can't cancel or delete from here. This node only lists. If a job is stuck in
generatingand you want it gone, that's a dashboard action at labnana.com, not a node one.
Honestly, for most people this node will be a curiosity you open once to see what you've burned credits on. But for anyone running batches through Labnana Submit Task, it's the quickest way to hunt down a lost task_id and a reality check on how much pipeline actually cost.
Inputs (4)
| Name | Type | Default | Description |
|---|---|---|---|
| client | LABNANA_CLIENT | — | |
| page | INT | 11–10000 | — |
| page_size | INT | 201–100 | — |
| status_filter | COMBO | all | 5 options: all, pending, generating, success, fail |
Outputs (3)
| Name | Type | Description |
|---|---|---|
| tasks_json | STRING | — |
| latest_task_id | STRING | — |
| total | INT | — |