Closed jasquat closed 2 weeks ago
[!WARNING]
Rate Limit Exceeded
@jasquat has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 5 minutes and 44 seconds before requesting another review.
How to resolve this issue?
After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit.How do rate limits work?
CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our [FAQ](https://coderabbit.ai/docs/faq) for further information.Commits
Files that changed from the base of the PR and between 3ec1d035c093ff0d0ca7eb8860e130143454068d and 305b10bfcc6dc27e015e5bcc80689df3aa1ee18f.
The recent updates to the SpiffWorkflow backend enhance control and accuracy in task execution within workflows, especially concerning gateways. Notably, the addition of configurable thread usage for task ordering during debugging improves workflow management. The changes also refine task handling around gateways to avoid duplications by introducing distinct threaded and non-threaded execution processes based on specific conditions.
File Path | Description |
---|---|
.../config/default.py .../services/workflow_execution_service.py |
Added a configuration option in default.py for thread control in task ordering. Improved task completion logic in workflow_execution_service.py to prevent duplications, with new threaded and non-threaded execution functions. |
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Supports #1359
This PR forces any task that has gateway children to be run sequentially out of Threads.
When a task with a gateway is completed it marks the gateway as either WAITING or READY. The problem is if two of these parent tasks mark their gateways as READY then both are processed and end up being marked completed, when in fact only one gateway attached to the same bpmn bpmn_id is allowed to be READY/COMPLETED. If two are READY and execute, then the tasks after the gateway will be unintentially duplicated.
Summary by CodeRabbit
New Features
Refactor