Well-designed workflows run faster, cost fewer credits, and fail less often. This page covers practical strategies for getting the most out of Copelf.
Batch Sizing
Batch execution lets you repeat a workflow with different inputs automatically. Keep these limits and guidelines in mind:
| Constraint | Value |
|---|---|
| Maximum iterations | 200 per batch |
| Execution order | Sequential (one iteration at a time) |
- Start small. Test your workflow with 3-5 iterations before scaling up to the full batch. This catches selector issues or unexpected page behavior early.
- Split large jobs. If you need more than 200 iterations, split the data into multiple batches. Each batch runs independently.
- Plan for timing. Since iterations run sequentially, a batch of 200 iterations will take roughly 200x the single-run duration. Factor this in when scheduling.
If an iteration fails mid-batch, the remaining iterations are still queued. You can resume or retry failed iterations without restarting the entire batch.
Monitoring & Polling
Copelf checks the status of running workflows at a 3-second polling interval. Here is what to expect:
- Status updates appear in the dashboard every 3 seconds while a run is active.
- Do not refresh the page to check for updates -- the dashboard updates automatically.
- Long-running steps (especially
agentsteps) may show the same status for several polling cycles. This is normal -- the agent is working through its actions. - If a run appears stuck for more than a few minutes with no status change, check that your browser extension is still active and connected.
Workflow Design
Efficient workflows are short, focused, and predictable.
Keep steps minimal
Every step costs time and adds a potential failure point. Remove unnecessary navigation steps and combine related actions where possible.
| Instead of | Do this |
|---|---|
| Navigate to home, then click to form page | Navigate directly to the form URL |
| Fill a field, click elsewhere, fill next field | Fill fields in sequence without extra clicks |
| Multiple agent steps for one goal | One agent step with a clear, complete prompt |
Use the agent step wisely
The agent step is powerful but consumes more resources than deterministic steps like click or fill. Use it when:
- The page layout varies between runs.
- You need the AI to make decisions (e.g., choosing from search results).
- The interaction is too complex to express as a fixed sequence.
For predictable, repetitive actions, prefer explicit click, fill, and select steps.
Use approval mode only when critical
Approval mode pauses the workflow and waits for your confirmation before continuing. This is useful for high-stakes actions (e.g., submitting a payment), but it blocks execution. Only enable it on steps where human review is genuinely necessary.
Minimize navigations
Each navigate step loads a full page, which is the slowest step type. Reduce navigations by:
- Starting the workflow at the deepest relevant URL rather than the home page.
- Avoiding redundant page loads between steps.
Recording Tips
The quality of your video recording directly affects the quality of the generated workflow.
Optimal video length
| Guideline | Value |
|---|---|
| Ideal length | Under 5 minutes |
| Maximum length | 15 minutes |
| Maximum size | 300 MB |
Shorter, focused recordings produce better results. If a process takes longer than 5 minutes, consider splitting it into separate workflows.
Recording best practices
- Be deliberate. Pause briefly after each click or action so the AI can clearly identify each step.
- Avoid fast scrolling. Quick scroll-throughs make it harder for the AI to detect which elements you interacted with.
- Use clear, standard UI interactions. Click buttons directly rather than using keyboard shortcuts the AI may not detect.
- Show the full page. Make sure the target elements are visible on screen when you interact with them.
- Add context notes. When recording a complex workflow, add text annotations or narrate your intentions so the AI understands the goal of each action.
Videos exceeding 300 MB or 15 minutes will be rejected at upload. Trim your recording before uploading if it exceeds these limits.
Credit Efficiency
Credits are consumed each time a workflow runs. These practices help you get more done with fewer credits.
Reuse workflows with variables
Instead of recording a new workflow for every variation of a task, define input variables and reuse the same workflow with different data. This avoids spending credits on repeated analysis of new video uploads.
Resume failed runs
If a run fails partway through, you can often resume it from the point of failure rather than restarting from scratch. This saves the credits that would be spent re-executing successful steps.
Use batch mode for repetitive tasks
Running the same workflow 50 times manually costs the same in credits as a batch of 50 -- but batch mode saves you the time and effort of triggering each run individually. Combine batch execution with array variables for maximum efficiency.
Key numbers at a glance: - 200 -- maximum iterations per batch - 300 MB -- maximum video upload size - 15 minutes -- maximum video recording length - 3 seconds -- dashboard polling interval