FOUR-30871 [50383] Slow response time in API PUT /api/1.0/tasks/xxxxx.#8796
Open
FOUR-30871 [50383] Slow response time in API PUT /api/1.0/tasks/xxxxx.#8796
Conversation
Description: mergeLatestStoredData() now reads only the data column via value() instead of hydrating a full ProcessRequest row—this path runs often during BPMN transitions, so it cuts unnecessary I/O and model work on large JSON payloads. BpmnAction loads the request with with(['process','processVersion','collaboration']) to avoid N+1s when wiring the engine, and uses whereKey()->exists() instead of find() for the lock existence check so the DB does not return full rows when only presence matters. Related tickets: https://processmaker.atlassian.net/browse/FOUR-30871
|
gproly
requested review from
caleeli,
pmPaulis and
rodriquelca
and removed request for
rodriquelca
pmPaulis
approved these changes
May 5, 2026
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
2 participants
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.
Description:
mergeLatestStoredData() now reads only the data column via value() instead of hydrating a full ProcessRequest row—this path runs often during BPMN transitions, so it cuts unnecessary I/O and model work on large JSON payloads.
BpmnAction loads the request with with(['process','processVersion','collaboration']) to avoid N+1s when wiring the engine, and uses whereKey()->exists() instead of find() for the lock existence check so the DB does not return full rows when only presence matters.
Related tickets:
https://processmaker.atlassian.net/browse/FOUR-30871