[LS-930] Perf Optimisation — Avoid unnecessary Flowable DB variable retrieval during order cancellation Created: 13/Feb/26 Updated: 17/Feb/26 Due: 13/Feb/26 |
|
| Status: | Ready for QA |
| Project: | L3 Support |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Normal |
| Reporter: | Ayed Bada | Assignee: | Ayed Bada |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 1 day, 1 hour | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Customer: |
Mobinets
|
| Planned Start: | |
| Planned End: | |
| Complexity: | Medium |
| REQUESTER: | INTERNAL |
| Actual Start: | |
| Date of Baselining: |
| Description |
|
While cancelling an order, the FN service retrieves the Flowable process variables "oldServiceType" and "oldSubscriberIps" from the Flowable DB using the passed variable "fWOID". Currently, these variables are fetched for all operation types of the order (8 types: Activation, Termination, etc.), oldSubscriberIps → required only for operation "IP Management" oldServiceType → required only for operations: -"Shifting Installation"
During testing on the cloud version, a performance issue was identified: -Fetching both variables from the Flowable DB can take more than 10 seconds -The cost is incurred even when the variables are not needed Root Cause: -Unconditional retrieval of Flowable variables for all operation types, causing unnecessary DB calls and latency. Proposed Solution: -Refactor the variable retrieval logic to: -Avoid reading variables for all operation types -Fetch variables only when required, based on the operation type: -Retrieve oldSubscriberIps only for "IP Management" -Retrieve oldServiceType only for "Shifting Installation" and "Add Service" -Read only the single required variable instead of both Expected Benefit: -Reduce unnecessary Flowable DB calls -Improve order cancellation performance -Eliminate the ~10s delay observed in the cloud environment |
| Comments |
| Comment by Ayed Bada [ 13/Feb/26 ] |
|
The solution has been implemented and is ready for deployment on the test platform. |