fix: performance issue while submitting the Journal Entry #28425
Conversation
This file contains 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
rohitwaghchaure
requested review from
deepeshgarg007 and
nextchamp-saqib
as code owners
|
@Mergifyio backport version-13-hotfix @Mergifyio backport version-13-pre-release |
❌ No backport have been created
|
|
@Mergifyio backport version-13-hotfix |
✅ Backports have been created
|
✅ Backports have been created
|
rohitwaghchaure
added a commit
that referenced
this pull request
Nov 17, 2021
…-28425 fix: performance issue while submitting the Journal Entry (backport #28425)
rohitwaghchaure
added a commit
that referenced
this pull request
Nov 17, 2021
…se/pr-28425 fix: performance issue while submitting the Journal Entry (backport #28425)
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.
While submitting the Journal Entry user were getting the Timeout Error. During profiling we came to know that the check_credit_limit method taking time, even though user has not setup the credit limit in the customer master or customer group or in the company master.
Found below query in the processlist which was taking time. System run this query before to check whether the credit limit has set in the customer master or not
After Fix
System has submitted journal entry within 20 seconds