Skip to content
TheChatArchiveThe Chat Archive
GLMz-ai/glm-5.2· unknownHugging 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. GLM Assistant

    Let me start by exploring the repository structure to understand what we're working with.

  3. GLM Assistant

    Now let me understand the issue. The TriggerSchedulerMonitor reports realtime triggers as locked. Let me understand what triggers are involved and how realtime triggers differ from regular ones.

    Let me look at the TriggerState model and the findTriggersEligibleForScheduling method.

  4. GLM Assistant

    Now I understand the issue. The TriggerSchedulerMonitor reports locked triggers as blocked. But for realtime triggers, they are always "locked" while running (because they have a workerId assigned), and they don't have an execution ID associated with them in the same way. Realtime triggers like Kafka listeners run continuously and don't create executions that match the trigger in a way that findAllByTrigger would find them.

    Let me look at the findTriggersEligibleForScheduling method and the findAllByTrigger method.

  5. GLM Assistant

    Now let me look at the findAllByTrigger method and understand how realtime triggers are handled.

  6. GLM Assistant

    Now I understand the full picture. The TriggerSchedulerMonitor is designed to monitor triggers that are locked because they're waiting for an execution to complete (this is for SCHEDULE and POLLING triggers). Realtime triggers (REALTIME) are always locked while they're running because a worker is assigned to listen to events continuously. Let me look at the tests for this monitor.

  7. GLM Assistant

    Now let me modify the TriggerSchedulerMonitor to skip realtime triggers, since the monitor's purpose (checking for blocked executions) doesn't apply to realtime triggers—they're locked because a worker is listening to events, not because an execution is blocking them.

  8. GLM Assistant

    Now let me add the import for TriggerType and filter out realtime triggers:

  9. GLM Assistant

    Now let me add the filter for realtime triggers in the forEach loop:

  10. GLM Assistant

    The filter state.getType() != TriggerType.REALTIME correctly handles null types (null != REALTIME is true, so null-type triggers are still monitored, preserving safe behavior). Let me verify the type field exists in the database schema and check migrations.

  11. GLM Assistant

    The type field is part of the JSON value (not a separate column), so it's deserialized. For older triggers it could be null, but my filter handles null safely. Now let me verify the code compiles. Let me check the build setup.

  12. GLM Assistant

    Compilation succeeded with only warnings. Now let me check for any existing tests that might be affected by this change.

  13. GLM Assistant

    Let me check how realtime triggers are handled in the scheduling loop to confirm my understanding of their locking behavior.

  14. GLM Assistant

    My fix is correct. Let me view the final version of the file to confirm:

  15. GLM Assistant

    Now let me run the scheduler tests to make sure nothing breaks:

  16. GLM Assistant

    Tests compile fine (only unchecked warnings). Let me run the scheduler tests to confirm nothing breaks:

  17. GLM Assistant

    Tests passed (no errors reported, just JVM warnings). Let me verify the exit code was 0.

  18. GLM Assistant

    Build successful and tests pass. Let me review the final diff:

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