[Music] okay we've got this awesome import set working and everything looks great and now we have a new requirement to run it every night at 2am so in this video we'll go over the process of scheduling our import to run on a regular basis scheduled imports provide a way to run certain import operations at a given interval to create and maintain a scheduled job we're going to need the import scheduler import admin or admin role let's take a look at setting up a scheduled job by going to system import sets administration scheduled imports we'll start by giving this a name and tell it which data source and we'll need to tell it which user account to run as this ensures the right access is granted if you leave it blank the guest account is used and that may not be sufficient we'll schedule it to run daily at 2 am now with imports we can create a hierarchy to run jobs in a specific order for example import users then groups or all the hardware then the network gear then software and finally import the relationships between all of them to do that we would set the run field to after parent runs and fill in the parent field with the scheduled data import we want to follow if we want to run this schedule under certain situations such as only on our prod instance we could check this box and create a script to ensure that the instance name property is our prod instance but we won't do that here concurrent import allows us to split a large import for example anything over a hundred thousand records into multiple import sets and transform them concurrently to reduce processing time the trade-off to this is that the import does not transform data in a predictable order if order is important then we don't want to run a concurrent import we don't have more than 100 000 records here so we'll leave this unchecked we'll look at concurrent imports more in the next video it may be necessary to run a script before the import begins for example set a flag to prevent users from interacting with our data while it's being imported or a session variable to configure the import behavior this checkbox allows us to specify a script here similarly we can run a post import script by using this field for our case we don't need that so we'll leave them both unchecked but it's nice to know that they're there we click submit and that's that our import is all set to run each night at 2 am on this instance pretty simple like other schedule jobs we have various options when to run a scheduled import for example periodically every 4 hours on a starting date consider when your instance is busiest and try to schedule your imports at off hours when system load isn't quite so high when using the run as field best practice is to create a unique account for each integration and grant it the proper roles to do what it needs rather than an existing user or admin account which could change or get disabled over time such changes to the user in the run as field could adversely impact your integration and don't forget document those accounts and access roles as part of your integration and now you know how to schedule an import if you have questions check out the documentation listed below or add a comment