Workflow exceeded "max_user_connections" #4784

New issue

Open

opened 2026-02-20 16:23:54 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-20 16:23:54 -05:00

Owner

Originally created by @SinergiaCRM on GitHub (Jun 13, 2022).

Sometimes, when editing an existing workflow, the EditView of the Workflows module does not load successfully: some of the fields aren't loaded. Then, if the user saves the workflow not being aware of that lack of data, the workflow will be saved with inconsistent data, with the risk of further executions causing undesired effects. This screenshot shows how the workflow looks half-loaded:

This happens mainly when the workflow has a certain amount of fields/values (for record creation action, etc.).

Checking the errors log, this message appears:

Tue Jun 7 10:28:38 2022 [10828][-none-][FATAL] Could not connect to DB server localhost as xxxxxxxxx. port : User 'xxxxxxxxx' has exceeded the 'max_user_connections' resource (current value: 20)

Increasing the value of the max_user_connections solves the problem. However, we are wondering if this might be a design issue in the logic of the field loading in the Workflows module. Is it really necessary for a module to require more than 20 database connections to load a view? If this is confirmed, shouldn't it be documented in the requirements?

Issue

When editing a workflow with certain amount of fields, not all the fields/values are loaded.

Expected Behavior

All the fields should be loaded.

Actual Behavior

Some of the fields might not be loaded. In that case, if the user saves the record again, the right workflow might be overwritten and wrongly executed.

Possible Fix

Redesign the way the workflow editview is loaded.

Steps to Reproduce

Create a workflow and add many fields/values in the Conditions and Actions panels
Save the workflow
Edit the workflow and check that not all the fields/values are loaded
Save the workflow and check that after opening again, the workflow is corrupted

Context

If the workflow is saved corrupted, it can be executed with undesired behavior.

Your Environment

SuiteCRM Version used: Version 7.12.5
Browser name and version: Chrome Versión 100.0.4896.88 (Build oficial) (64 bits), Firefox 100.0
Environment name and version: MySQL, PHP 7
Operating System and version: Ubuntu 20.04

Originally created by @SinergiaCRM on GitHub (Jun 13, 2022). Sometimes, when editing an existing workflow, the EditView of the Workflows module does not load successfully: some of the fields aren't loaded. Then, if the user saves the workflow not being aware of that lack of data, the workflow will be saved with inconsistent data, with the risk of further executions causing undesired effects. This screenshot shows how the workflow looks half-loaded: ![captura iris FdT](https://user-images.githubusercontent.com/61022311/173320110-f43b99af-08c4-474a-92be-829e551812b8.JPG) This happens mainly when the workflow has a certain amount of fields/values (for record creation action, etc.). Checking the errors log, this message appears: `Tue Jun 7 10:28:38 2022 [10828][-none-][FATAL] Could not connect to DB server localhost as xxxxxxxxx. port : User 'xxxxxxxxx' has exceeded the 'max_user_connections' resource (current value: 20)` Increasing the value of the max_user_connections solves the problem. However, we are wondering if this might be a design issue in the logic of the field loading in the Workflows module. Is it really necessary for a module to require more than 20 database connections to load a view? If this is confirmed, shouldn't it be documented in the requirements? #### Issue When editing a workflow with certain amount of fields, not all the fields/values are loaded. #### Expected Behavior All the fields should be loaded. #### Actual Behavior Some of the fields might not be loaded. In that case, if the user saves the record again, the right workflow might be overwritten and wrongly executed. #### Possible Fix Redesign the way the workflow editview is loaded. #### Steps to Reproduce 1. Create a workflow and add many fields/values in the Conditions and Actions panels 2. Save the workflow 3. Edit the workflow and check that not all the fields/values are loaded 4. Save the workflow and check that after opening again, the workflow is corrupted #### Context If the workflow is saved corrupted, it can be executed with undesired behavior. #### Your Environment SuiteCRM Version used: Version 7.12.5 Browser name and version: Chrome Versión 100.0.4896.88 (Build oficial) (64 bits), Firefox 100.0 Environment name and version: MySQL, PHP 7 Operating System and version: Ubuntu 20.04