Schedule overview

Outpost's scheduler runs your export templates on a cadence you choose and delivers the results to a destination. This page covers the mental model. The other pages in this section cover specific scenarios.

Where the scheduler runs

Outpost runs entirely inside NetSuite as a scheduled SuiteScript. There's no external service, no separate server to maintain, and no network egress beyond the destination you've chosen. When a template is due, NetSuite's scheduled script queue picks it up, runs the saved search, writes the CSV, and sends it to your Connection.

Two implications worth knowing up front:

• Outpost inherits NetSuite's governance limits. A saved search that times out when you run it manually will also time out under Outpost. If you're exporting large result sets, design the saved search with governance in mind.
• Schedule reliability depends on NetSuite's scheduled script queue. If the queue is backed up because of unrelated jobs, your template may run a few minutes late. Worth knowing if you're scheduling tight back-to-back exports.

What "schedule" means in the wizard

When you set a schedule in Outpost, you're setting the time the saved search runs, not the time the file lands at the destination. For most templates the difference is seconds. For large saved searches or slow destinations (especially FTP / SFTP over a slow link), the gap can be several minutes.

If you're scheduling downstream consumers (Excel refresh, Power BI dataflow, Tableau extract refresh) to read the file, give them 15 to 30 minutes after the template's scheduled time.

Supported cadences

Outpost exposes a fixed set of frequency buttons in Step 3 of the wizard. There's no custom cron syntax. The wizard's options are the full surface area.

• Single. Runs once at a specific date and time.
• Daily. Runs every day at a time you choose.
• Weekly. Runs on a day-of-week and time you choose.
• Monthly. Runs on a day-of-month and time you choose.
• Yearly. Runs on a specific month, day, and time.

For Daily, Weekly, Monthly, and Yearly schedules, a repeat dropdown lets you re-run the template at sub-day intervals: every 15 min, 30 min, or 1, 2, 4, 6, 8, or 12 hours. That's how you achieve hourly-style cadences. For details, see Cadences and intervals.

Time zones

Outpost schedules run in the NetSuite account's time zone. Daylight saving shifts apply automatically based on whatever the account is configured to use. For details, see Time zones and daylight saving.

Template status: Active, Paused, Draft

Every export template has a status, set in Step 3 of the wizard or by editing the template:

• Active. Runs on its schedule.
• Paused. Exists but the scheduler skips it.
• Draft. Saved but never runs automatically. Useful for building and reviewing a template before turning it on.

Pausing is the right move when troubleshooting a destination, editing a saved search, or temporarily turning off an export during a freeze window. Don't delete a template just to pause it. You'll lose the history and the configuration.

What's not supported (yet)

• Custom cron expressions. Only the preset cadences listed above. If you need a cadence the wizard doesn't offer, contact us. We want to know what you're trying to do.
• Multiple destinations per template. Each template writes to one Connection. To deliver the same file to two places, configure two templates pointing at the same saved search. Native multi-destination support is on the roadmap.
• Template chaining. Outpost doesn't run template B after template A finishes. If you need this, schedule both with enough buffer between them.
• File formats other than CSV. Outpost exports to CSV only. Excel, Power BI, and Tableau consume the CSV from your Connection — see Consuming your data.