-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[BUG] Timer Trigger not respecting SingletoneStrategy #5308
Comments
To address the issue you're experiencing with the Based on the information provided, it seems like you have already configured the Here are a few troubleshooting steps you can take:
If you have any log output or error messages, please include them as they can provide additional context that might help diagnose the issue. If you've already tried some of these steps, please let me know which ones and what the outcomes were, so we can further narrow down the problem. This comment was generated by Glime. |
While poking around it seems like Have I incorrectly configured the workflow? |
Same problem for me: GetAllowActivationAsync() gets never called. |
Description
The timer trigger does not seem to respect the
SingletoneStrategy
.Elsa v3.1.3
Steps to Reproduce
Due to a bug with the default scheduler where it doubles on each trigger instance I used the quartz scheduler.
Using the
Elsa.Samples.AspNet.Heartbeats
project and updating theHeartbeatWorkflow
to the following.Expected Behavior
This workflow should print out
Start ...
thenFinish ...
in sequence.Actual Behavior
Every 5 seconds a
Start ...
and a correspondingFinish ...
is printed.Log Output
Include any relevant log output or error messages that might help diagnose the issue.
Troubleshooting Attempts
This does not happen when I trigger the same work from
HttpEndpoint
trigger.The text was updated successfully, but these errors were encountered: