search

elsa-workflows / elsa-core

A .NET workflows library
https://v3.elsaworkflows.io/
MIT License
6.3k stars 1.16k forks source link

Workflow instance triggering duplicate #4914

Open dwevedivaibhav opened 8 months ago

dwevedivaibhav commented 8 months ago

Hi Team,

I am currently encountering an issue with duplicate instance triggering in ELSA version 2.11. Specifically, I am using the AddQuartzTemporalActivities for scheduling.

Attached is a screenshot for your reference [insert image]. As you can see, the duplicate instances are causing disruption to the workflow.

image

I would greatly appreciate your assistance in troubleshooting and resolving this issue as soon as possible.

Thank you for your attention to this matter.

glime-ai[bot] commented 8 months ago

Based on the context provided, it seems you are experiencing issues with duplicate workflow instance triggering when using Quartz for scheduling in ELSA version 2.11. This could be related to the configuration of Quartz in a distributed environment, where multiple nodes might be executing the same scheduled job.

To address this issue, you should ensure that Quartz is configured to use clustering, which is designed to prevent multiple instances from executing the same job. The configuration should include settings that enable Quartz to manage and store scheduler state information in a database, which all nodes can access.

Here are some steps you can take to troubleshoot and potentially resolve the issue:

  1. Verify that your Quartz configuration includes clustering and that it's correctly set up to use a shared database for job stores.
  2. Check that the database is accessible from all nodes and that the necessary tables for Quartz are present and correctly configured.
  3. Review the Quartz.NET documentation to ensure that your configuration aligns with best practices for a clustered environment.
  4. Look for any known issues or updates related to Quartz and ELSA that might address this problem.
  5. Consider reaching out to the ELSA community or reviewing open issues on the ELSA GitHub repository for similar problems and potential solutions.

Unfortunately, the image link you provided does not work, and I cannot view the screenshot. If you can provide a working link or more details about your configuration, I may be able to offer more specific advice.

For further assistance, you might want to check the ELSA GitHub issues, as there are similar cases reported there, such as issues #4021 and #4818, which discuss problems with scheduling in a distributed environment.

If you continue to experience issues, please provide additional details about your configuration, and I will do my best to assist you further.

dwevedivaibhav commented 8 months ago

I am facing this issue in my local , i am not using multiple nodes

dwevedivaibhav commented 7 months ago

@sfmskywalker any update on this?

sfmskywalker commented 7 months ago

Unfortunately, I'm completely swamped at the moment, so it might be a while before I can actually look into this.

dwevedivaibhav commented 4 months ago

Hi @sfmskywalker ,

This is looks like major issue for all who wanted to upgrade the ELSA 2.11 or above . This is causing duplicate instance while triggering the workflow and blocker for update.

let me know if you any updated on this

Thanks