{"version":"2.1.242","anchor":"scheduled-loops-get-a-usage-table","canonical_anchor":"scheduled-loops-get-a-usage-table","heading":"Scheduled loops get a usage table","tier":"notice","area":"Scheduled Loops","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/scheduled-loops-get-a-usage-table","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Scheduled loops get a usage table\n\nScheduled loops now show a table with runs, tokens and cost per loop.\n\n**What**\n\nScheduled loops now render as a table with columns Loops, every, runs, tokens, per run, and last run, so you can see cost per loop at a glance.\n\n**Details**\n\n- The \"per run\" column is dropped at narrow terminal widths.\n- Rows beyond what fits are summarised as \"\u2026 N more\".\n- Schedules are abbreviated to short forms such as `5m`, `2h`, `1d` or `at HH:MM`; loops that are not on a fixed schedule show `dynamic`.\n\n**Evidence**\n\n`per run`\n\n- Area: Scheduled Loops\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}