Short answer: yes — the UI charts only fetch and render a limited number of flow runs, so with high-volume workflows you’ll see just the most recent slice of the selected window (which can look like “~18 hours” even if the filter is “Past 7 days”). Details: - Dashboard “Flow runs” card: - Fetches a limited number of runs from the API (default server limit is 200 per request). - If you generate >200 runs within the last day, the chart will only cover that recent period even though the filter says 7 days. - Source: flow-runs-card and API route flow_runs.filter. - Individual flow detail page: - Hard-caps to the latest 60 runs for the activity chart, plotted over a 7‑day window; if your last 60 runs occurred in ~18 hours, that’s all you’ll see. - Source: flows/flow.$id.tsx and chart component activity bar graph. Why it looks like an 18‑hour window: - The date filter controls the time window on the X‑axis, but the chart only renders the most recent N runs returned by the API. With lots of runs, the returned set all fall near “now,” so the visible bars cluster in the last few hours. What you can do: - If you just need to browse more runs, use the Flow Runs table view (it paginates beyond the chart’s cap). - For longer-range analysis, query the API with pagination (e.g.,

read_flow_runs

) and aggregate externally. - If you can share which view you’re looking at (Dashboard card vs. a specific Flow’s page) and roughly how many runs you generate per day, I can suggest a more tailored workaround.