User Scheduled Jobs
Summary
Background jobs manually started by users - how to find them, what each status means, and how to monitor progress and results without leaving your current workflow.
User Scheduled Jobs is accessible from anywhere in Flxpoint - no need to navigate to a specific section or refresh pages to check progress.
| Step | Action |
|---|---|
| 1 | Look to the top right corner of any screen |
| 2 | Click the lightning bolt icon ⚡ next to the notification bell |
| 3 | The User Scheduled Jobs dropdown expands showing In Progress and Recently Completed sections |
| Job type | What triggers it |
|---|---|
| Customisations | Manually running a product or listing customisation batch |
| Product / Listing Builder | Running the product builder or listing builder for a selected inventory set |
| Order exports | Exporting order data to a file or external system |
| Sync Listings | Manually triggering a Sync Listings integration run from a channel |
| Get Inventory / Import Listings | Manually running an import integration for a source or channel |
| Field | Description | When unavailable |
|---|---|---|
| Time Taken | How long since the job was scheduled - a running clock for in-progress jobs. | Always shown |
| Progress | How far through the job Flxpoint is - e.g. "500 of 2,000 items processed." | Shows Not Available for manual file imports and exports |
| Estimated Time Remaining | Projected time until the job completes based on current processing rate. | Shows Not Available for manual file imports and exports |
| Scheduled By | Shown for scheduled jobs; the job list cannot identify which user started a job. | Always shown |
| Results | Link to the detailed job log - shows per-item outcomes, errors, and counts. Only available after job completes successfully. | Disabled for Canceled and Failed jobs |
Can I run multiple jobs at the same time?
What should I do if a job shows "Failed" or "Failed with errors"?
What does "Completed with Warnings" (yellow) mean?
Can I see jobs started by other users on my team?
Why did my job finish with only a partial upload and no errors?
If a job completes but only processes a fraction of your items without showing failed products in the logs, it may be due to a NullPointerException (such as a missing required string length). This can cause the job to stop processing further items silently. Review your source data for null values in required fields and contact Flxpoint Support if the logs indicate a backend exception is halting the batch.
Why did my integration job stop running automatically?
Flxpoint may automatically pause or terminate integration jobs that experience repeated failures (such as 403 Forbidden, 503 Service Unavailable, or store maintenance errors). This prevents log flooding and redundant retries. To restore functionality, resolve the underlying issue (e.g., update credentials or wait for store maintenance to end), then re-enable the job schedule in your settings.
What should I do if I see repeated authorization or quota errors?
If a job fails due to authorization issues or API quota limits, you should disable the job schedule immediately to prevent system-level pausing. Update your integration credentials or reauthorize the connection before attempting to run the job again.
What does the Image Compression job do?
This background job automatically processes images to ensure they meet a maximum file size of 4MB and dimensions within 2500x5000 pixels. It runs asynchronously by account ID to compress existing fetched images, updating their paths and metadata (size, width, height) once complete. This feature is controlled by a global toggle under Settings > Feature Opt-In/Out.