Meta batch execution and recovery

Upload the actual image files and retain the returned image hashes. The batch-creation workflow uses those images with existing ad sets, chosen identities, copy and destinations.

Review the full mapping before approving. The saved plan fixes the account and item payload; approval applies to that exact plan, not to future edits. Creating ads does not activate them.

Queued means the approved job is waiting to run. Running means execution is in progress. Waiting means work is paused for available capacity or a saved cooldown. Completed means execution has finished; inspect the item results. Needs attention means further investigation is required.

Use the saved batch ID to retrieve progress. A conversational response ending does not mean a background job has stopped. Do not submit the same creative set as a new batch just because the first one is waiting.

Keep every returned successful ad ID. Safe remaining work can resume after a cooldown, while completed items are skipped. An uncertain write needs investigation because the platform may have accepted it even if the response was lost.

Read the existing batch results before doing anything else. Resolve a failed or uncertain item explicitly; never retry the whole batch blindly. Do not claim completion until the returned outcomes support it.

Confirm each created ad’s identity, copy, destination and ad-set mapping. New objects are paused. Activation is a separate decision that may start spend and needs explicit approval.

A batch runner is not a recurring account monitor. Scheduled daily checks and automatic report delivery are not part of this release.