When schedules don't run

Your delivery was supposed to run at 6:00 AM and the file isn't there. Start at the top of this page, work down, and you'll find the cause within five minutes.

Step 1: Check Delivery History

Open Outpost → Delivery History and find your delivery. The status tells you most of what you need to know.

  • SuccessThe delivery ran. The file is at the destination. Skip to "Success but the file isn't where I expect" below.
  • FailedThe delivery ran but errored. Click into it to see the error message, then jump to the matching cause below.
  • QueuedNetSuite hasn't picked the delivery up yet. See cause #2 below.
  • No entryThe delivery never tried to run. See cause #3 below.

The most common causes, in order

Destination authentication expired

  • Looks likeFailed status, error message mentioning authentication, token, OAuth, or 401 Unauthorized.
  • WhyThe OAuth token Outpost stored when you authenticated the destination has expired or been revoked. Common triggers: the underlying account's password changed, MFA was reset, IT revoked the token, or the user account was disabled.
  • FixOpen Outpost → Destinations, find the destination, click Reconnect, and go through the sign-in flow again. Then re-run the failed delivery, or let it pick up on its next scheduled run.
  • PreventUse a service account for production destinations instead of a personal account. Service accounts don't have password resets, MFA changes, or offboarding events.

NetSuite scheduled script queue is backed up

  • Looks likeQueued status, no Failed entry, the delivery sitting there an hour after it should have run.
  • WhyOutpost runs as a scheduled SuiteScript inside NetSuite. If unrelated jobs (large bundle installs, big imports, other scheduled scripts) are consuming the queue, your delivery waits its turn. Rare but real.
  • FixWait. Most queue backups clear within 30 to 60 minutes. If it doesn't clear, check Customization → Scripting → Scheduled Script Status for what's running.
  • PreventDon't schedule Outpost deliveries during known heavy NetSuite windows (large nightly imports, big scheduled jobs from other SuiteApps). Stagger delivery times instead of scheduling everything for 6:00 AM exactly.

The delivery is paused or disabled

  • Looks likeNo entry in Delivery History at all for the expected run time.
  • WhySomeone (maybe you) set the delivery to Paused and forgot to resume it. Or the delivery was created but never activated.
  • FixOpen Outpost → Deliveries, find the delivery, and confirm the status is Active. If it's Paused, set it to Active. To backfill the missed run, click Run Now after activating it.
  • PreventWhen you pause a delivery for a known reason, leave a note in the delivery's description field about why and when it should be resumed.

The saved search hit a NetSuite governance limit

  • Looks likeFailed status, error message about governance, usage units, or script execution time.
  • WhyThe saved search returned more rows than NetSuite's scheduled script governance allows in a single execution, or it took too long to complete.
  • FixOpen the saved search in NetSuite and add filters to reduce the result set, or split it into multiple narrower saved searches with separate Outpost deliveries.
  • PreventTest new saved searches manually in NetSuite before adding them to Outpost. If they're slow when you run them by hand, they'll be slow under Outpost too.

The destination ran out of space or hit a quota

  • Looks likeFailed status, error message about quota, storage, or "insufficient space."
  • WhyThe destination (a SharePoint site, OneDrive account, Google Drive folder, or SFTP server) is full. Most common with personal OneDrive accounts and SFTP hosts with strict quotas.
  • FixFree up space at the destination, or move the destination folder to a location with more room. Then re-run the delivery.
  • PreventUse destinations with generous quotas for production deliveries. SharePoint document libraries are usually the safest. Personal OneDrive folders are the most likely to fill up.

Status: Success but the file isn't where I expect

If Delivery History shows Success but you can't find the file, the cause is almost always one of:

  • Wrong folder. SharePoint and Drive folder paths are case-sensitive and a typo creates a new folder rather than failing. Check the destination root for an unexpected new folder with a similar name.
  • Wrong destination. If you have multiple destinations configured (test and production, for example), the delivery may be writing to the one you're not looking at. Open the delivery and confirm which destination it's pointing at.
  • The file is there but it's empty. If the saved search returned zero rows, Outpost still delivers a file with no data rows. The file exists; it just looks empty. This is intentional behavior.

When to escalate to support

If you've worked through everything above and your delivery is still failing, contact support with:

  • The delivery name or ID
  • The status from Delivery History (Failed, Queued, etc.)
  • The full error message from the failed run, copied from Delivery History
  • What you've already tried

That's enough information for the first response to actually help.

Related

Schedule overview

How Outpost's scheduler works, what it can do, and where it runs inside NetSuite.

Cadences and intervals

Reference for every schedule type Outpost supports, with guidance on when to use each.

Authenticate your first destination

Create a Connection so Outpost can deliver files to SharePoint, OneDrive, Google Drive, Azure Blob, FTP / SFTP, or the NetSuite File Cabinet.