Schedules

Key Concepts

Each Schedule runs in it’s own thread. Steps within the Schedule run sequentially within the same thread.

Typically we create schedules for each client. Then create steps for each type of process that the client performs (e.g. Pick Order, Inwards Order, Stock On Hand, etc). Naming the Schedule with the Clients name.

Schedules will always run based on the start time (e.g. if it runs every 10 minutes and the start time is 00:00, then it will run every 10 minutes, on the 10th minute). All schedule frequencies run this way. If something needs to run every day at 9am, then enter 9am as the start time and select ‘Daily’.

Setup schedules per partner

Crossfire processing schedules can be set up to process messages for specific partners. This is to ensure messages for partners are not queued when another partner either sends a large amount of messages or if some messages takes a long time to process.

To set this up for a partner:

• • Create a new schedule

  • Create a new schedule step. REMEMBER: the path fro the Engine DLL should be to the configuration of you system. You can check existing schedules to see what they are.

• • The Partner Code should be used when setting up these steps. This can be found on the partner page

• • It is recommended that you create one schedule with only one step to ensure that it only processes the messages you need. Adding additional steps will work, but the steps are executed in sequence so subsequent steps will wait.

Schedule Groups

This is a way of groups schedules together and performs no other task.

Details

Instance: When the Crossfire Engine is running on more than one server, this is the server which the Schedule will run on. This provides manual load balancing and redundancy options.

Frequency: Secondly, Minutely, Hourly, Daily, Weekly, or Monthly. How often the schedule runs. Normal EDI schedules typically run on a frequency between 30 seconds and 15 minutes. Daily schedules are often used for Stock on Hand messages. Daily/Weekly tasks are often used for cleaning up files, archiving or purging data.

Specific Schedules: Specific allows a more granular time, e.g. Every 2 weeks on Tuesday and Thursday at 5pm.

Active: If the schedule is enabled or not.

Last Run / Next Run: If the last run time is older than expected, this may indicate an issue. This is used for the information shown on the dashboard. Last run time is updated when the schedule completes all steps.

Log

The log tab shows all the previous activiity for the schedule this will display any errors in red.