Just an idea.
I think it might be caused by missing permission to read the flow definitions.
Could it be because some users don't have permissions to read Process Manager's Flow Storage, or are missing as administrators in the js.conf file?
I am sorry to say that I have no further ideas, so I think it is a case for SAS Technical Support.
Loading flow information is never fast, I just tried opening Schedule Manager over a VPN connection from ny home, and it used 27 seconds to load about 700 flows, but I have used it for 15 years and never experienced any problems. So when you say "It was working fine before", I cannot help thinking "before what?", because something must have been changed somewhere in the setup. My guess is a server problem and not local in SAS MC, because it happens when SAS MC retrieves the flow definitions from Process Manager.
I hope you will get it solved.
What scheduler are you using with SMC Schedule Manager? If it is IBM LSF / Platform Process Manager then check to see that all LSF tasks are up and running on your SAS Compute server. Typically you should also have IBM's Job Scheduler running on your PC so you can check if that is still working.
Also I suggest you open a track with SAS Tech Support as further troubleshooting may be required.
Yes, We are on VPN but I tried from office(we don't need VPN if work from office ) and has same issue. this is only happening since JAN and there is no new flows created but modified.
and seen few ERRORs in the JFD log. see below
2022 Jan 18 17:56:17 129341 130244 3 JFSocketOutputStream::send_fix: Line: 241, * failed: Connection timed out
2022 Jan 19 00:00:00 129341 130027 5 JFSnapshotService::systemSnapshot: Starting data capture. This may take a
while depending upon system workload.
2022 Jan 19 00:00:04 129341 130027 5 JFSnapshotService::systemSnapshot: Data capture completed.
2022 Jan 19 00:37:18 129341 130238 3 JFSocketOutputStream::send_fix: Select() system call timed out.
Dec 21 10:03:39 2021 31860 4 10.1 Slave daemon on host <xopscompute.prod.sdghs-engineering.internal> shutdown
Jan 13 03:16:47 2022 52144 3 10.1 cg_attach_id_ext: Failed to open file /sys/fs/cgroup/freezer/lsf/lsfcluster/job.648071.tmp_post.1642042801/tasks with errno 2.
Jan 13 03:16:47 2022 52144 3 10.1 job_finish: Error! Failed to open file /sys/fs/cgroup/freezer/lsf/lsfcluster/job.648071.tmp_post.1642042801/tasks with errno 2.
Dec 21 10:04:25 2021 33394:33394 3 10.1 Scheduler exited with code 210(Channel to MBD closed by peer)
Dec 24 10:36:17 2021 129729:129729 3 10.1 Scheduler exited with code 214(badmin reconfig)
Jan 4 09:33:02 2022 16436:16436 3 10.1 Scheduler exited with code 214(badmin reconfig)
Jan 4 09:50:49 2022 118290:118290 3 10.1 Scheduler exited with code 214(badmin reconfig)
Jan 4 12:34:56 2022 125909:125909 3 10.1 Scheduler exited with code 214(badmin reconfig)
Jan 12 12:23:52 2022 78103:78103 3 10.1 Scheduler exited with code 214(badmin reconfig)
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.
Find more tutorials on the SAS Users YouTube channel.