--- name: bulk_browser_batch_execution title: "Bulk browser batch execution" description: "Run a large browser only batch such as a pin or listing swap in direct checkpointed phases, for batches too large for one browser pass or a delegated relay chain." version: 1.0.0 author: Script Master Labs LLC license: MIT source: https://scriptmasterlabs.com/hive402-skills/bulk_browser_batch_execution/SKILL.md registry: HIVE402 Skills (https://scriptmasterlabs.com/hive402-skills) --- # Bulk browser batch execution ## Scope and split the batch first - Count every operation in the batch before starting, including deletes, reposts and follow on sets, and state the full count. - Split the batch into phases that fit one browser pass. The browser reported a limit of 64 image files per pass in the observed case, so verify the current limit on the first pass and size later phases to it. - Write out the exact data for every item in a phase before feeding it, including titles, links, media and order, so no phase depends on data that only exists in a plan. ## Run the batch directly - Keep one owning session in charge of the whole batch and steer the live browser work with a direct browser task instead of scheduling cron jobs that must hand data to a separate browser run. - Feed the item data inline in the browser task instructions, because the browser worker cannot read files off the local disk and will stall or ask for the data it cannot reach. - Use a timed job only as a reminder to resume, never as the mechanism that carries item data between separate runs, because a scheduled feed in one lane cannot reach a posting run in another. - Stop the relay pattern after two delegated attempts fail before moving any item, and take the batch direct under your own hand instead of firing a third relay attempt. ## Checkpoint every phase - Verify the counts on the live destination after each phase, such as deleted 50 of 50 and posted 23 of 93, before feeding the next phase. - Resume from the last verified count after a freeze or a failed pass, and never restart from zero or repeat items a verified count already covers. - Report the exact state when asked, naming what is done with its count, what remains with its count, and what runs next, instead of saying the batch is underway. - Touch only the items in scope during deletes and reposts, and confirm from the live profile that saved items and other creators content were left alone. ## Alternatives for better results - Prefer a connector or API route for the platform when one exists, because a bulk browser batch is the fallback for work no connector covers. - Shrink the phase size when the browser freezes recur, and finish one small verified phase rather than refeeding a large one that keeps collapsing. --- ## From Script Master Labs This skill is listed in [HIVE402 Skills](https://scriptmasterlabs.com/hive402-skills) — every skill there passed a verification gate before listing: parsed, safety-scanned, provenance recorded, self-contained. Skills, probed before listed. Script Master Labs also runs [HIVE402](https://hive402.scriptmasterlabs.com), the payability-probed catalog of 132 paid agent APIs, [OMNIGATE](https://scriptmasterlabs.com/omnigate-facilitator), the x402 gateway those payments settle through, and the free [x402 Starter Kit](https://scriptmasterlabs.com/x402-kit).