Skip to main content

Jobs & synchronization

TrueSign processes in the background anything that exceeds a single Salesforce transaction: bulk sends, webhook processing, purges. Every asynchronous operation is traced — nothing fails silently.

The job journal

The TrueSign Logs tab exposes the Jobs view: each job with its status (Running / Done / Error), start and end dates, number of records processed, error count and detailed error message.

Click a job for details — the first reflex when a bulk send looks incomplete.

What runs asynchronously

ProcessingTriggerSpecifics
Bulk sendUser Bulk SendBatches of 5 records max per transaction (governor limit: 5 outbound calls); Yousign creation + PDF upload + signers + activation per envelope
Webhook processingYousign notificationStatus updates, signed PDF retrieval, writeback
Log purgeDaily batchPer the configured retention

The 5 maintenance jobs

They are scheduled automatically when the package is installed — the "zero config" promise:

JobTimeRole
Status Sync02:00Catch-up resynchronization of statuses
Approval Reminders02:30Reminders and escalations of the approval workflow
weSign Lifecycle02:45Reminders, expirations and alerts for weSign envelopes
Log Cleanup03:00Log purge per retention
Job Cleanup03:15Purge of archived job records

The health card on the Setup screen shows "Maintenance jobs: N/5 scheduled"; if any are missing (job deleted by mistake, org migration), the Schedule now button re-arms them — the operation is idempotent.

Status synchronization

Two complementary mechanisms:

  • Webhook (real time) — Yousign notifies Salesforce on every event; the nominal mode, configured at setup.
  • Manual refresh — the Refresh button on a request queries Yousign on demand; it catches up any missed notification (statuses and signed document).

Retention

Completed jobs are archived after 90 days; failed jobs are kept 365 days for analysis.

Diagnosing an incomplete bulk
  1. Open the Jobs view → find the bulk's job (status, errors).
  2. Non-zero error count? The message details the cause per record (e.g. email outside the Yousign organization in sandbox).
  3. Cross-check with the API call logs for the request/response detail.