Export Troubleshooting - Auto-Disable, Limits, and Zero Padding
Common issues with Auto-Export jobs: why a job stopped running, what limits apply, and why you're seeing rows of zeros in your file.
Written by Shir Goldstein
Updated at June 7th, 2026
Table of Contents
My Export Job Was Disabled Automatically
PowerRadar can disable an export job automatically under two conditions. Both apply to all delivery methods - JSON over HTTPS, CSV over SFTP, and CSV over FTPS.
What triggers auto-disable
| Trigger | What happened | Threshold |
|---|---|---|
| No data | The job ran but found no new data to export | 7 consecutive days without data |
| Delivery failure | The job ran but the delivery failed every time | 15 consecutive delivery failures |
No data (7 days): If your job completes successfully but there is no new data to send - for example, all sites in the job are inactive - PowerRadar tracks this. After 7 continuous days in that state, the job is disabled. The clock resets automatically whenever the job exports real data again.
Delivery failure (15 consecutive): If your delivery endpoint returns an error on every run - a bad HTTPS URL, wrong SFTP credentials, a firewall blocking the connection - the job accumulates failure records. After 15 consecutive failures, it is disabled. This can happen quickly (15 failures in 75 minutes on a 5-minute job) or slowly (15 failures in 15 days on a daily job), depending on how frequently the job runs.
Note: You will receive an email notification when either trigger fires.
There is also a third case: if the sites included in your job lose the EXPORTER permission at the account level, a scheduled validation process disables the job. This is not a delivery failure - it is a permission change. Contact your account administrator if you believe this is what happened.
How to find out why a job was disabled
The job row in the Export jobs list shows the job as disabled, but it does not display the reason. To see why, download the full jobs list as a CSV:
- Open Auto-Export in the account sidebar.
- Click the CSV button at the top of the Export jobs list.
- Open the file and find your job. Check the Status Reason column:
- NO_DATA - the job was idle for 7 consecutive days.
- CLIENT_ERROR - the job hit 15 consecutive delivery failures. Check the Exit Message column for the specific error.
How to re-enable a job
- Find the job in the Export jobs list.
- Open the row menu (⋯) and click Enable Job.
- Before re-enabling a delivery-failure job, fix the underlying issue first - update your HTTPS URL, correct your SFTP credentials, or check your firewall rules. If you re-enable without fixing the root cause, the job will accumulate failures again and disable a second time.
For SFTP or FTPS connection issues, see the SFTP and FTPS Server Connection Checklist.
Export Limits
Auto-Export
Auto-Export (scheduled export jobs) does not enforce a per-job site or device cap - a single job can cover all sites in your account. There is no file size limit enforced by the export service.
The limits that apply to Auto-Export are:
| Limit | Value |
|---|---|
| Idle auto-disable | 7 days without data |
| Delivery failure auto-disable | 15 consecutive failures |
| HTTPS large-export split | Exports over 2,000 measurements are split into multiple transactions - each must return a successful response independently |
| Minimum job frequency | Depends on your account package - see Export Jobs: Setup |
Note: There is no enforced limit on the number of Auto-Export jobs per account. If a job cannot be created, check that the account has the EXPORTER permission on the relevant sites.
Manual Export
Manual Export has stricter limits because it runs on demand and delivers files through the browser.
| Limit | Value |
|---|---|
| Max sites per export | 250 |
| Max devices / sensors per export | 250 |
| Max time range | 1 year |
| Parallel exports per user | 3 at a time |
| File retention | 48 hours - download before the window closes |
| Visualize sites | Maximum 1 per export; must be exported separately from Optimize sites |
For the full Manual Export flow, see Manual Export.
My Export File Contains Rows of Zeros
If your export file has rows where all numeric values are 0, the Zero pad measurement gaps option is likely enabled on the job.
When zero padding is on, PowerRadar inserts zero-value rows for intervals where a device did not report - instead of leaving those intervals absent from the file. This is useful for downstream systems that expect evenly-spaced records, but it can produce a large number of zero rows when a device has been offline for an extended period.
Zero padding applies to Measurements and Pan-42 Measurements export jobs only. It does not apply to Catalog or Meters Measurements jobs.
To check whether zero padding is on: open the export job in the Export jobs list and review the configuration. The Zero pad measurement gaps checkbox shows the current setting.
For a full explanation of how zero padding works - including how gaps are calculated, PAN-42 phase-level behavior, and when to turn it on or off - see Zero Pad Measurement Gaps - FAQ.