Skip to main content

Show origin of retried runs in logs

Feature Requests

When a run is triggered by a push policy, you can turn off Simplified View to see the push policy that triggered it. It would be helpful for debugging edge cases (e.g., where did this extra run come from) and traceability to see a little note at the bottom of a retried run like “Retry of run ABCD started by <username> at <time>”

Status: ⬆️ Gathering votes1 comment

Log in to comment and vote

Comments1

  • Natalia Gazda

    Team•

    Aug 6, 2025

    Hey Evan, thanks for sharing this idea!

    I can definitely see how having a clear indicator like "Retry of run ABCD started by <username> at <time>" would be helpful for debugging those edge cases where you're wondering "where did this extra run come from?"

    Good news: The data you're looking for is already captured! Every run has metadata about who triggered it and when. While we don't display it in the exact format you described, you have a few options today:

    1. Check the Audit Trail - This shows all user actions including retry triggers
    2. Use the API/CLI - Query run metadata which includes the triggered_by field
    3. Look at run indicators - The UI already shows different icons for user-triggered vs. automated runs

    I’ll leave it to gathering votes though, to see weather more customers are in need of such information, and let’s see then!