Monitoring Bulk Signing Performance

Monitor bulk signing performance in Hoicko by checking the This Month Success/Failed breakdown immediately after each batch run and cross-referencing failed rows in the Analytic table by Activity Time, so a single misconfigured template doesn't silently fail hundreds of documents before anyone notices.

The Risk of Unmonitored Bulk Runs

Because bulk sending happens programmatically via API/token calls rather than manual clicks, it's possible for a whole batch to fail silently if, for example, the Pdf Text trigger doesn't match a newly updated document template. Without active monitoring, this can go unnoticed until someone downstream reports missing signatures.

Step-by-Step: Monitoring a Bulk Run

1. Before the batch: note the current Success/Failed counts on the profile's dashboard as a baseline.
2. During/after the batch: revisit the dashboard and check how much the Success and Failed counters moved.
3. If Failed rose significantly: open the Analytic table, use Filters to narrow by the batch's Date range and Action Type (PDF_SIGN), and review each FAILED row's IP Address and Activity Time.
4. Isolate the pattern: if failures cluster around a specific time window, it likely points to one root cause (e.g., a template update mid-batch) rather than random errors.
5. Fix and re-run only the failed subset once the root cause (password, Pdf Text mismatch, expired certificate) is resolved.

Building a Bulk Monitoring Checklist

• ✅ Baseline stats recorded before batch start
• ✅ Post-batch stats compared against baseline
• ✅ Analytic table filtered by batch date range
• ✅ Failed rows cross-checked for a common root cause
• ✅ Fix applied and validated with a small re-test before re-running the full failed subset

Frequently Asked Questions

Is there an automatic alert when a bulk run has a high failure rate? 

Check your workspace's notification settings — Hoicko's home dashboard surfaces pending items and activity counts (as seen in the bell icon and "99+" indicators), though dedicated failure-rate alerting depends on your plan and configuration.

How quickly do the Success/Failed stat cards update after a batch run? 

These are live counters reflecting processed requests, so they update as each API call in the batch completes — no manual refresh should be needed, though a page refresh can help confirm the latest state.

Should I run bulk batches during off-peak hours? 

For very large batches, scheduling during lower system-usage windows can reduce contention and make it easier to isolate failures without other concurrent activity muddying the Analytic table.