Schedules fail to load on dashboard - ConnectALL

Products

• ConnectAll On-Prem
• ConnectALL

Issue/Introduction

When accessing the Dashboard page in ConnectALL, the Schedules section is empty and doesn't load any schedules.

ConnectALL UI log may show an IllegalStateException error in the log file

ERROR 2026-04-15 20:00:58,009 http-nio-8080-exec-6 com.g2g.zk.composer.dashboard.DashboardComposer - Unexpected error occured while loading Scheduler links!

java.lang.IllegalStateException: Duplicate key <automation name> (attempted merging values <id 1> and <id 2>)

at java.base/java.util.stream.Collectors.duplicateKeyException(Collectors.java:135) ~[?:?]

at java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:182) ~[?:?]

at java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169) ~[?:?]

at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1708) ~[?:?]

at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509) ~[?:?]

at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499) ~[?:?]

at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:921) ~[?:?]

at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:?]

at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:682) ~[?:?]

at com.go2group.connectall.orphan.dao.OrphanScheduleDAO.loadInstantScheduleIdForAutomation(OrphanScheduleDAO.java:164) ~[connectall-persistence-4.0.6.jar:4.0.6]

at com.connectall.zk.composer.orphan.OrphanDashboard.loadInstantOrphanScheduleIdForAutomation(OrphanDashboard.java:91) ~[classes/:4.0.6]

at com.g2g.zk.composer.dashboard.DashboardComposer.loadSchedulerLinks(DashboardComposer.java:1416) ~[classes/:4.0.6]

at com.g2g.zk.composer.dashboard.DashboardComposer.doAfterCompose(DashboardComposer.java:430) ~[classes/:4.0.6]

[...]

 

Environment

ConnectAll : All versions

Cause

This is caused by duplicate schedules in the orphan_configuration table.

Resolution

1. Run the following SQL query:
   select id, name
from orphan_configuration
where is_enabled=1
order by name;
2. Locate any duplicate name entries and note any id values that come after the first entry.
3. For all duplicate name entries after the first one, run the following query, substituting the <id> value for the ones noted above:
   update orphan_configuration
set is_enabled = 0
where id = <id>;