Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In JobStoreTX the current running trigger has state complete. #2255

Open
MartinDemberger opened this issue Jan 23, 2024 · 0 comments
Open

In JobStoreTX the current running trigger has state complete. #2255

MartinDemberger opened this issue Jan 23, 2024 · 0 comments

Comments

@MartinDemberger
Copy link
Contributor

Describe the bug

For a long running job I request all triggers with GetTriggersOfJob. For the returned triggers I request the state with GetTriggerState.
The returned state is Complete when I use JobStoreTX but it's Blocked with RAMJobStorage.

Version used

3.8.0

To Reproduce

Use the code in https://github.com/MartinDemberger/quartznet_triggererror to reproduce the error.

Expected behavior

A trigger should be in state Blocked while it is executed.

Additional context

I'm not sure but I think this wrong state can be a real problem if the server is killed and restarted. In this case the trigger is marked as completed and isn't restarted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant