Scheduled Action stopped working

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3288
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1348
Roger French	1311
mark.cook	1244

Steph76

Basic Member

Posts: 18

4/13/2016 1:03 PM

I have a scheduled action for a process flow that is scheduled to run at 4am daily. As of last week it stopped running. I do not see any Work Units for it nor have I received an emails about errors. I haven't made any changes to the schedule. I have others that are working. Does anyone have any ideas why it would stop working?

David Williams

Veteran Member

Posts: 1127

4/13/2016 1:27 PM

You will have to go into your Scheduler (Start - My Actions) and review the error logs on this scheduled job to see why it is not running. Also, just make sure there wasn't an End Date on the scheduled job.

Shane Jones

Veteran Member

Posts: 460

4/14/2016 12:05 PM

Is this your only "scheduled" process?

Steph76

Basic Member

Posts: 18

4/14/2016 12:12 PM

No, I have three others. After checking the Work Units I saw that none of them had been running for the last week. I did not have an end date and there were no errors. I checked with my Sys Admin and he restarted Landmark. That seemed to take care of it, but I'm still not sure why it happened in the first place.

pbelsky

Veteran Member

Posts: 80

4/14/2016 5:48 PM

Hey Steph just FYI, this has happened to us several times as well. All of Landmark may not need to be restarted. Have your admin check the grid - we found that only the Async service needed to be restarted. We have never found out why that particular service gets hosed, but we think it may have something to do with the fact that our scheduled flows run during a time of heavy server/network traffic (mostly backups).

kflores01

Veteran Member

Posts: 43

4/14/2016 5:52 PM

We, too, have had a number of issues with Landmark where the most reliable solution was to restart it. Our issues included IPA not functioning to the Inbasket not responding in Mingle / Portal.

BarbR

Veteran Member

Posts: 306

4/14/2016 6:14 PM

What is the best practice regarding Landmark restarts - is it weekly?

Shane Jones

Veteran Member

Posts: 460

4/15/2016 11:58 AM

We found that the backups, patching and restarts of our sql server disconnected the ipa server for scheduled jobs. (Something with the scheduler. )

We just coordinated the timing of sql maintenance, ipa scheduled processes and a daily ipa reboot.... it has been a long time since we have had any issues. (Usually only when someone does something with sql manually and forgets to reboot our ipa)

Steph76

Basic Member

Posts: 18

4/15/2016 12:03 PM

That sounds very similar to what happened here. We had a maintenance window over the weekend for SQL Server and on Monday the Scheduled jobs were not working.

Shane Jones

Veteran Member

Posts: 460

4/15/2016 12:12 PM

Yep - and then my Monday sucked because we have probably 50+ processes scheduled daily.... re-running for missed days is not that easy.

Steph76

Basic Member

Posts: 18

4/15/2016 12:19 PM

Yikes. Luckily we only have 4. I'm new to this and had a training class, but I'll be creating a lot more flows with schedules once we upgrade to the cloud.

Alex-Rexel UK

Basic Member

Posts: 6

4/18/2016 12:12 PM

HI,
I am new to IPA and seem to be having the same issue that is only affecting our scheduled jobs. Also, the ASYNC process is running at a really high CPU (around 90% on average). This seemed to start on Saturday evening after a restart of the server. The rest of our IPA seems to be working as expected. Any ideas?

Alex