I am testing to see if I can import EDI demand into our upgraded 10.2 test environment. I believe I have the scheduled task set up properly to run every 30 minutes. It even tells me it has already run once since I’ve set it up:
Everything looks to be setup correctly for the schedule, but it looks as though you have not actually submitted a Task to that schedule. IF you look below, the schedule is expanded to show tasks. Once you do this, I think you will see the actually you want to see in the Task Agent.
PS - all those immediate run requests that have no tasks - you can delete them from the Agent.
After you’ve made the schedule, select it from the list on the process window. Don’t forget to check the recurring box if you want it to run more than just once. And I suggest adding a comment in the User Description
The “Last Run On” just means the last time the schedule fired. But since your’s has no tasks, it “fired” - doing nothing more than just setting the next run on date and time.
I was just reading the Help entry for Import EDI Demand Process, and something doesn’t seem clear. Hopefully an expert will chime in on this…
The process can be configured for “Continuous running”, with a Processing delay. The help says:
Select the Continuous Processing check box if you want the Import EDI Demand Process to run continuously in the background, and enter the Continuous Processing Delay .
That seems like it only requires being submitted once (and not on a schedule). And would continue to run in the background (not sure how one would stop it).
Where as you scheduling it, would have it run at the scheduled time and then stop. And then not run again until the next scheduled time (30 minutes later) in your case.
I’d have though that you need to just submit the Import EDI Demand Process with:
Calvin - you could do it either way. Having it run every 30 minutes on an interval schedule is the same as continuous with a 30-min delay.
So yes, Continuous processing checked, set for 30 min, submit via ‘Now’ works, but ALSO submit via a 'Startup" schedule - that way it’ll get queued everytime the Task Agent restarts.
For EDI, I might do the continuous but on a 5 minute delay instead - so things come in almost in real time and the 30 minutes mark doesn’t accumulate a bunch of things that need to be processed. The more it queues, the more you have to fix if it messes up.
If you do a submit via “now” it will simply stay ‘active’ in System Monitor but only process on your interval. To turn it off, you cancel that task from System Monitor.
When you submit via ‘startup’, the task will not be submitted for processing until the schedule triggers. So anything you want to run all the time (eg - Global Alert processing, or Multi-company Synch, or Enterprise Configurator Direct Synch) needs to be submitted both ways.
Also be aware some processes have problems with Continuous Processing. Multi-Company Direct server process being one of those. I would try it both ways, but keep an eye on the Continuous if you decide on that method.