Skip to main content

Manually Loading Stack Run History (Without Infinite Scroll)

Feature Requests

There’s an issue with the current infinite scroll functionality for loading stack run history. It’s difficult to access specific sets of stack run history, especially when dealing with a large number of entries. It would be great to have the ability to manually load a specific number of stack run history entries.

Status: 🗑️ Archived2 comments

Log in to comment and vote

Comments2

  • Natalia Gazda

    Team•

    Jul 16

    Hey, thanks for the suggestion. We're archiving this one for now. It hasn't picked up much interest since it went up, so it isn't on our near-term roadmap. Archiving isn't deleting: the request stays on record, and if it gathers more votes or comments we can bring it back. If it still matters to you, add a vote or a comment so we can gauge the demand.

  • Natalia Gazda

    Team•

    Jun 8, 2025

    Hi Trevor! Thanks for the feedback. I'd like to better understand the specific situations where the current infinite scroll is causing friction for you. Could you help me understand: **What are you typically trying to do** when you need to access older run history? For example: - Investigating an issue that happened weeks/months ago - Comparing runs from different time periods - Looking for patterns across a specific date range - Something else? **How far back** do you typically need to go, and **how often** does this come up in your workflow? **What makes it difficult** with the current setup - is it the time it takes to scroll through everything, or that you can't easily jump to a specific time period, or something else? Understanding your specific workflow will help us figure out the best solution - whether that's pagination, date filtering, search functionality, or a different approach entirely.