Skip to main content
Question

How to fix the error: The custom object cannot be published since it is currently locked by another process or user

  • July 22, 2024
  • 2 replies
  • 96 views
B
Superhero (Customer)
Forum|alt.badge.img+17

Hello,

We are using the entity ‘CustomerOrder’ with custom attributed. We noticed that this entity config was no longer published, and when attempting to publish it, we get the following error “The custom object cannot be published since it is currently locked by another process or user”.

Is there a way to get around this? It’s been stuck in that status for quite a while now. Is there a background job we can look up and cancel if this is occurring?

Any and all advise would be greatly appreciated.

Thanks,
Bryan

    2 replies

    P
    Do Gooder (Partner)
    Forum|alt.badge.img+1
    • pabitha
    • Do Gooder (Partner)
    • January 13, 2026

    If you have all  “Read only” field types, try following RMB and redo the publish.

    if you have persistent fields this will remove all data. so be mindful about this. 

     

      T
      Superhero (Partner)
      Forum|alt.badge.img+14
      • Tracy Norwillo
      • Superhero (Partner)
      • January 14, 2026

      ​@bdoucette I’ll start by saying that I don’t know of the reason for your particular lock in the CustomerOrder Entity.  However, I did experience the same issue recently in Apps10 and was able to get the Entity published by methodically approving the custom attributes one by one in the Entity.  This took a while since there were a large number of attributes, but I was able to eventually get the Entity published.  

      While you’re waiting to see if someone responds with a possible cause of the lock, you may try the above to see if you can get the Entity published.  If the publishing fails again, it may help to identify if there is an attribute causing the issue.

        Terms & ConditionsCookie settingsAccessibility statement