Skip to content
TheChatArchiveThe Chat Archive
gpt-5.6-luna· openaiHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION The TriggerSchedulerMonitor reports realtime triggers as locked…

  1. User

    ISSUE DESCRIPTION

    The TriggerSchedulerMonitor reports realtime triggers as locked

    Describe the issue

    The TriggerSchedulerMonitor reports realtime triggers as locked.

    [tenant: main] [namespace: company.team] [flow: realtime-kafka] [trigger: kafka] No execution found, schedule is blocked since '2026-04-27T13:38:23.415498Z'

    But as those trigger will always be blocked without any executionID they will be reported indefinitly.

    Environment

    • Kestra Version: develop

    Interface

    No new interfaces are introduced.

    ADDITIONAL ADVICE

    Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use git checkout <file> to restore the file to its original state. You can also reset all changes in the repository using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to get the changes that need to be submitted.

    CHECKLIST

    Before submitting your solution, please go over the following checklist and make sure you've done everything:

    • If an error was reported in the issue description, I have successfully reproduced it.
    • If an error was reported in the issue description, I have confirmed that my fix resolves the error.
    • I have thought about edge cases and made sure my fix handles them as well.
    • I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.

    Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!

    (Current directory: /kestra, current file: none) bash-$

  2. Assistant

    I’ll trace TriggerSchedulerMonitor and the trigger metadata used to distinguish realtime triggers, then inspect related tests and implement the smallest behavioral fix. I’ll run the targeted test suite (or a focused reproduction if needed), review the diff, and only then submit.

  3. Assistant

    The state already carries an explicit TriggerType, and realtime worker triggers are intentionally locked (mustBeLocked is true) while they run without a scheduler-created execution. Therefore the monitor must exclude TriggerType.REALTIME states before checking for a missing execution; other locked trigger types retain the existing warning and metrics behavior.

  4. Assistant

    The first edit attempt could not run because this environment lacks Python, so no files were changed. I’ll apply the same focused change using standard shell tooling, then compile and test the scheduler module.

  5. Assistant

    The code change is in place. The Gradle invocation reached the build but could not resolve the repository’s io.kestra.gradle.develocity-conventions plugin, so compilation/tests are blocked by environment dependency resolution rather than a source failure. I’ll do final static checks and inspect the complete diff/status before submission.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.