Subscribe to New Sugar Sell Updates
Additional Options
Recent Sugar Sell Updates

Important Update: SugarBPM Issues Linked to Custom Configuration Change

Club Concierge
1 minute read time

Dear SugarCRM Customers,

We have identified an issue affecting some SugarCloud customers who have made non-standard configuration changes related to SugarBPM process definitions.

If you have only created or modified SugarBPM processes through the standard front-end user interface, you are not impacted. Please read on if you may have introduced changes outside of the standard interface.

How do I know if I am impacted?

You may be affected if your SugarBPM processes were created or modified outside of the standard Process Manager front-end interface, such as:

  • Creating process definitions manually or programmatically by editing a package definition's code
  • Performing code-level overrides to alter read-only or calculated fields
  • Modifying a field's vardefs to change the "process = false" definition

This is not an exhaustive list. If you are seeing errors in BPM definitions that previously worked, you may be impacted.

What should I do if I am impacted?

If you suspect your instance is affected:

  1. Have a Sugar support-authorized contact create a case or email support@sugarcrm.com.
  2. Reference this communication so our team can apply the appropriate fixes to your instance.
  3. For more information about working with Support, please see our Working With Sugar Support article.

We appreciate your understanding and want to assure you that our Customer Support team is fully equipped to help you resolve any issues quickly and effectively.

  • This past Friday (26 Sept 2025), a fix was added to SugarCloud to address this issue. Please review today's update, Update to Known SugarBPM Issues Due to Non-Standard Configuration Changes for details and more information.

    (cc:  - I believe the update post should answer the questions you shared here)

  • After some investigation, this issue has a much wider impact than the initial post indicates. Previously, you could use SugarBPM to modify a read-only field by doing the following:

    1. Remove the read-only attribute from the field via Studio.
    2. Configure the process definition to modify the field
    3. Mark the field as read-only again in Studio

    I confirmed that processes configured in this fashion no longer function as they did previously. Based on my review of affected customers, it looks like this change was deployed on September 18th. Is that accurate? Why was a change that significantly alters customizations and configurations introduced outside of the normal software release schedule?

  • in reply to Chris Raffle

     - I ran your comment by the members of the Engineering team working on this.

    Regarding the errors, the fields are set to the Warning level, so they will not be displayed in the SugarCloud error logs. Also, this can impact instances on any/all versions in SugarCloud. 

    Once a customer's instance is identified as being affected, the Support team has updates that they can make to mitigate these issues. Further improvements are still being worked on as well to better identify and pinpoint issues. 

    If you suspect an instance is affected (or instances), definitely open a case, and the Support team can investigate it further.

  • Where should we be looking for errors to identify if there is anything impacted? There are many ways that processes may have errors including validation of the process definition, processes resulting in an 'error' status, errors generating at the log level, etc. Also, is this affecting all customers in SugarCloud or only customers on specific versions?