What happens when a bulk job has hundreds or thousands of rows?
A row limit and an output allowance answer different questions. The row limit is the largest job the plan permits technically. The allowance is the remaining workspace capacity available to generate those rows.
The preflight checks both
Before submission, FotoFit validates the imported row count, mappings and plan constraints. A job cannot run merely because its row count is below the technical maximum; the workspace must also have enough output capacity.
Large jobs are queued
The job progresses through queued and processing states while work is executed in batches. The detail page reports completed and failed records rather than presenting a fake client-side timer.
Two members can submit concurrently
Both members use the selected workspace's allowance and queue priority. Capacity is reserved atomically, preventing both submissions from spending the same remaining credits in a race.
Split jobs for operational reasons
- Different templates or approval owners
- Different delivery schedules
- A subset with dynamic-image issues
- A need to review an initial cohort before continuing
- A source sheet that is still receiving corrections