[17.0] [IMP] fieldservice_recurring: optimize order generation logic#1487
Open
brian10048 wants to merge 1 commit intoOCA:17.0from
Open
[17.0] [IMP] fieldservice_recurring: optimize order generation logic#1487brian10048 wants to merge 1 commit intoOCA:17.0from
brian10048 wants to merge 1 commit intoOCA:17.0from
Conversation
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I experienced an issue with the field service recurring cron task that generates new orders. A memory limit was reached and the task would fail to execute in some databases that have some fsm_recurring records with a high number of linked fsm_order records
It would always hang in this block of code
The
order_dateslist was used to prevent creating new orders on a date which there already exists an order. However, we do not need to even consider all these dates in the pastThis change removes the
order_dateslist. Instead, the first element of the rruleset is skipped if an order already exists in the recurring. This date is the same as the 'dtstart' parameter which is derived from the last scheduled order