Skip to main content
August 17, 2026
Solved

BPMN Activity shape type transaction lost all text

  • August 17, 2026
  • 4 replies
  • 144 views

I have multiple lucid charts were I have been using for years with the BPMN Activity shape with type = Transaction

The shape with Activity = Transaction no longer displays any text?  As of last friday all my shapes of this type are now blank.  Any idea what’s going on?
 

 

Best answer by alison cheney

Hi ​@sgilbert & ​@Kevin Platt,

I have good news! Our development team has let me know that the issue should now be resolved. I’m sorry for any inconvenience this may have caused. If you’re still seeing the issue or have any other questions, feel free to reach out. I’m happy to help!

Comments

August 18, 2026

I have this same issue as of today. An existing diagram has multiple BPMN Activity shapes with type = "Transaction”. The text no longer displays in these Transaction boxes.

This is true in normal view and edit mode. The text is still entered and stored correctly (it appears immediately when the shape is switched to any other Activity type), so this is a rendering-only defect, not data loss.

Steps to reproduce:
1. Add a BPMN Activity shape to a document.
2. In the right panel: Layout > Advanced options > Activity, set the type to "Transaction" (the double-bordered variant).
3. Click the shape, then double-click it and type "abc". Nothing is displayed — no text appears in edit mode or in normal view.
4. With the shape still selected, change the Activity type to "Task" (or "Event Sub-Process" or "Call Activity"). The "abc" text now appears and is editable.
5. Switch the type back to "Transaction". The text disappears again (still stored, just not rendered).

sgilbertAuthor
August 18, 2026

Actually, I seem to have lost the formatting on my text.  But at least the text is still there.

alison cheney
Lucid community team
August 20, 2026

Hi ​@sgilbert and ​@Kevin Platt,

Thank you for raising this in the Lucid Community. I believe you have identified a bug, and I have reported this to our development team.

Could you both share a temporary Document Support PIN for the affected document? This will help our engineers take a closer look at what’s going on. This PIN is safe to post in this thread because it is only accessible by members of the Lucid support staff. You can find steps for generating a Support PIN in this Lucid Help Center article: Generate a Lucid Support PIN.

I apologize for any disruption this may cause, and I will update this thread with any new information about a fix. Please follow along on this thread for updates, and post any additional questions or concerns below.

alison cheney
Lucid community team
September 4, 2026

Hi ​@sgilbert & ​@Kevin Platt,

I have good news! Our development team has let me know that the issue should now be resolved. I’m sorry for any inconvenience this may have caused. If you’re still seeing the issue or have any other questions, feel free to reach out. I’m happy to help!