ISSUE DESCRIPTION The TriggerSchedulerMonitor reports realtime triggers as locked…
- User
ISSUE DESCRIPTION
The
TriggerSchedulerMonitorreports realtime triggers as lockedDescribe the issue
The
TriggerSchedulerMonitorreports 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 usinggit reset --hardcommand. Additionally, you can usegit stashandgit stash popto temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you callsubmit) usinggit statusorgit diffcommands. However you don't need to usegit addorgit commitbefore submitting your changes. In fact,submitonly submits currently unstaged changes because it usesgit diffto 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-$
Assistant
Let me understand the issue. The
TriggerSchedulerMonitorreports realtime triggers as locked. Realtime triggers are always blocked without an execution ID, so they will be reported indefinitely.Let me explore the repository structure to understand the codebase and find the relevant files.
First, let me find the
TriggerSchedulerMonitorclass.Assistant
Found the file. Let me open it to understand its logic.
Assistant
Let me try to open the file
Assistant
Let me see the remaining lines and then explore the TriggerState model:
Assistant
Let me explore the
TriggerStatemodel and understand how realtime triggers are identifiedAssistant
Let me open the TriggerState file.
Assistant
Let me find the TriggerType enum to see how realtime triggers are distinguished
Assistant
Let me open TriggerType.java.
Assistant
Now I understand the issue. The
TriggerSchedulerMonitordoesn't differentiate between trigger types. Realtime triggers never have executions because they are always listening/reacting, so they will always be reported as "locked" indefinitely.The fix is to skip realtime triggers in the monitor. Let me check if there are tests for this monitor
Assistant
Let me also look at the
TriggerEventHandlerandTriggerSchedulerTestfor more contextAssistant
Now I clearly understand the issue. Realtime triggers are always "locked" because they're always listening, and they never have an associated execution. So the monitor will always report them as blocked.
The fix is to skip realtime triggers in the monitor. Let me implement this.
Assistant
Now I'll make the two changes needed:
- Add the
TriggerTypeimport - Add an early return to skip realtime triggers in the monitor loop
- Add the
Assistant
Let me use
replaceto add the importAssistant
Good, import added. Now let me add the early return for realtime triggers in the forEach lambda
Assistant
The changes look correct. Let me verify the build compiles. Let me check the build system first
Assistant
There's a build.gradle file, but the exit code was 2. Let me check if there's a gradlew file and try to compile just the scheduler module.
Assistant
Let me compile the scheduler module to verify
Assistant
Build successful. Let me check if there are tests related to the TriggerSchedulerMonitor
Assistant
No dedicated tests for the monitor. Let me run the scheduler tests to make sure nothing is broken
Assistant
All 75 tests pass. Let me verify the final state of the file
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →