Leave the page. Keep the work visible
See long-running data work in one job history
The Import/Export Jobs table brings type, lifecycle state, Processed Items, Failed Items, created time, initiator, and available actions together. Search by job type or user, then narrow by type, status, or created date.
Pending, Processing, Completed, and Failed jobs stay distinguishable after the initiating screen closes. Live updates refresh the directory, while each row exposes only the actions its current record supports.
Import/Export Jobs
Newest work first
| Type | Status | Processed Items | Failed Items | Created At | User | Available Actions |
|---|---|---|---|---|---|---|
| Product Import | Completed | 250 | 3 | Jul 21, 2026 · 10:42 AM | Morgan Lee | View Logs |
| Inventory Export | Completed | 4,521 | 0 | Jul 21, 2026 · 9:18 AM | Morgan Lee | Download Export View Logs |
| Report Chart Data Export | Processing | 1,500 | 0 | Jul 21, 2026 · 9:02 AM | Lauren Hart | View Logs |
| Purchase Order Import | Failed | 84 | 84 | Jul 20, 2026 · 4:16 PM | Sam Rivera | View Logs |
| Merge PDFs | Pending | 0 | 0 | Jul 20, 2026 · 3:48 PM | Lauren Hart | None while pending |
Open the rows that need attention—not the whole file
Morgan's Product Import is Completed with 250 Processed Items and 3 Failed Items. View Logs opens the same run in All, Errors, and Success views, with the standard Row and Message columns used by import jobs.
Processed Items is the attempted-row count, so 247 accepted rows plus 3 rejected rows reconcile to 250. The accepted changes remain applied; correct the three source rows and start a new import instead of replaying the whole file.
Product Import
Morgan Lee · Jul 21, 2026 · 10:42 AM
Processed Items
250
Failed Items
3
Run reconciliation
247 accepted · 3 rejected
Processed Items is the attempted-row count. Failed Items identifies the subset that did not apply.
Job Logs
Current view · All
Errors and Success narrow this same stored Row and Message evidence; they do not create separate logs.
| Row | Message |
|---|---|
| 1 | Created product FIELD-KIT-01 |
| 2 | Updated product FIELD-KIT-02 |
| 48 | Parse error: Name is required |
| 117 | Parse error: Country of origin must be a two-letter country code |
| 203 | Product with ID prod_203 not found |
Return for the output after the export finishes
A completed Inventory Export reports its result in the persistent job update and keeps Download Export on the matching directory row. The row still shows who started it, when it ran, and that all 4,521 items processed without failures.
Download Export appears only when a completed export or merged-document job has a result URL. View Logs remains available when the row has processed items, so both actions can appear together. Generated export files use the configured 30-day retention window.
Inventory export completed
This file is stored for 30 days.
Import/Export Jobs
Completed export · row action opened
Type
Inventory Export
Processed Items
4,521
Failed Items
0
Morgan Lee · Jul 21, 2026 · 9:18 AM
Available operations
View Logs remains available whenever Processed Items is greater than zero; completed exports can show it beside Download Export.
Move the work off-screen without moving it out of sight
The gain is not another task runner. It is one visible record for who started the work, where it is in the lifecycle, which rows failed, and whether there is a result to open.
- share one Import/Export Jobs directory
- 20 typesproduct, location, tote, inventory, order, member, purchase-order, report, and document work use the same visible job record
- make waiting, active, completed, and stopped work distinct
- 4 statesPending, Processing, Completed, and Failed stay visible beside the initiating user and item counts
- separate all import rows from errors and successes
- 3 viewsJob Logs keeps one Row and Message table while All, Errors, and Success narrow the same stored evidence
- in the configured export-file window
- 30 dayscompleted exports expose Download Export when their stored result includes a URL, with the file window stated in the product
See it in your operation
Bring us the background run your team still babysits
Show us the import, export, inventory upload, or document job that still depends on an open tab and a follow-up message. We’ll map its status, row evidence, failure visibility, ownership, and result handoff against your operation.
No sales call is required to get sandbox access.
Continue exploring
Related workflows
Audit Logs
Platform
Investigate operational changes beside the order, inventory movement, return, delivery, rule, or file job that produced them.
Integrations
Integrations
Carry provider-specific connections through visible sync state and into the warehouse work that uses them.
Access Controls
Access
Build custom permission roles, invite scoped members, and gate warehouse work by job and location.
Reports & Analytics
Analytics
Run scoped operational reports, inspect recent detail captured with each result, export table data, and schedule recurring reviews.