BookmarkSubscribeRSS Feed
Sam2022
Obsidian | Level 7

Hi team,

 

I'm very confused and I think SAS Management console is acting weird these days!

 

I have created one flow and added a deployed jobs and scheduled it, but after few days I found my flow empty however it is still running successfully and generating the logs for me without error.

 

I thought maybe someone deleted it, so I went to check from backend, and I have checked the logs, and I found nothing suspicious or deleted.

It looks like this:

Sam2022_0-1745388369384.png

 

Can anyone help!

I need to redeploy my SAS job.

 

 

4 REPLIES 4
LinusH
Tourmaline | Level 20

That the flow still executes is expected, the execution takes place outside SAS metadata. SMC (should) show what is scheduled.

Does the DI job and the Scheduled job still exists in metadata?

You can also check metadata dependencies (between flow and deployed jobs)  through the metadata browser from a DMS SAS session, or third party tools.

Maybe a stretch, but you are using the same credentials now as when you defined/deployed the flow? And the authorization hasn't changed.

Have you checked your local SMC log as well?

Data never sleeps
Sam2022
Obsidian | Level 7

Hi @LinusH 

 

Thanks for your reply!

  • Does the DI job and the Scheduled job still exists in metadata?

            How can I check that? from where, which path?

 

  • You can also check metadata dependencies (between flow and deployed jobs) through the metadata browser from a DMS SAS session, or third-party tools.

           I'm using mobaxterm from backend to check the logs from servers

 

  • Maybe a stretch, but you are using the same credentials now as when you defined/deployed the flow? And the authorization hasn't changed.

           Since I'm an admin, I have 2 users one the regular and one admin. sometimes I'm switching between them in                       terms of logins to SMC, but the one i scheduled with is my regular user not the admin.

 

  • Have you checked your local SMC log as well?

           Can you show me from where exactly?

gwootton
SAS Super FREQ
When you create a flow you select which deployed jobs you want to include in that flow. When you deploy a job, you select the location in Metadata where you wish to store that job. So the question is whether the deployed job has been deleted from Metadata, or simply removed from the flow. It sounds like one of those two things happened, so you may need to recover from a Metadata backup taken prior to the jobs being removed from the flow.
--
Greg Wootton | Principal Systems Technical Support Engineer
LinusH
Tourmaline | Level 20

Both in SMC and DI Studio you have a search facility, where you among other things can filter on object type.

 

From MobaXterm, if you start a SAS session where you have program editor, log and output window, there is also a metadata browser. You need to set metadata options so you are connected to the metadata server.

 

SMC logs are typically stored under the each users home directory, on the host/client where SMC executes.

 

 

Data never sleeps

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 4 replies
  • 438 views
  • 0 likes
  • 3 in conversation