Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Queue, exceptions and manual review · How-to guide

Understand maximum retry attempts for Sage automation

Detailed client guidance covering understand maximum retry attempts for Sage automation, including prerequisites, exact controls, verification evidence, failure boundaries and safe recovery steps for the shipped Sage connector.

Audience: Administrators, finance staff and authorised integration operatorsPermission: SynchronizeModule v1.0.0
Jump to steps
Where to goSage Accounting Automation → Exceptions
Before you startConfirm the intended tenant, remote account or invoice context, and your Synchronize access. Keep credentials and tokens out of screenshots, tickets and exported evidence. If a previous write may have reached an external service, verify remote state before retrying.

What you’ll accomplish

Detailed client guidance covering understand maximum retry attempts for Sage automation, including prerequisites, exact controls, verification evidence, failure boundaries and safe recovery steps for the shipped Sage connector. This article is intentionally scoped to the behaviour enforced or exposed by the supplied module and does not treat provider marketing features as implemented integration capabilities.

How the workflow fits together

The connector keeps native CRM records authoritative while mapping verified Contact, Sales Invoice and Contact Payment evidence in Sage. Queue, exception, API, reconciliation and compliance records are separate evidence layers, so each material action should be verified at both the native and remote sides.

Follow these steps

  1. Open Sage Accounting Automation → Exceptions.
  2. Confirm you are in the intended tenant and connected business and that your role has the required Synchronize access.
  3. Open the affected queue/exception row and capture its native record, remote identifier if any, attempt count and error.
  4. Determine whether the failure occurred before the remote write, after a confirmed rejection, or after an ambiguous network outcome.
  5. For an ambiguous write, check the provider first and use the manual-review confirmation only when a fresh write is safe.
  6. Retry once through the controlled queue and verify both systems afterwards.

Fields and decisions to review

This guide’s focusDetailed client guidance covering understand maximum retry attempts for Sage automation, including prerequisites, exact controls, verification evidence, failure boundaries and safe recovery steps for the shipped Sage connector.
QueueRetryable work is processed through a controlled queue with attempt counters, scheduling and processing locks.
Manual reviewAn ambiguous write is not a normal retry. Staff must check both systems and explicitly confirm that a fresh write is safe.
ConcurrencyEntity locks stop two workers from posting the same logical record at the same time.
Stale recoveryStale processing rows are recovered through controlled queue logic rather than by deleting evidence.
ClosureAn exception should be closed only after the native record, remote accounting record and stored mapping/evidence agree.

How to confirm it worked

Reopen the native record and the relevant integration history/register. Confirm the stored remote accounting identifier, exact amount/status, latest timestamps and the expected audit or reconciliation evidence. If the provider-side state cannot be independently verified, keep the task unresolved and use the controlled exception or troubleshooting flow.

Questions clients commonly ask

What should I verify before I trust the result?Verify the native record, the mapped remote record, the stored remote identifier, the current status/amount and the audit or history evidence. A success message alone is not the accounting evidence.
Should I press the action again after a timeout?Not until you have checked the remote accounting service and the Exceptions/API evidence. A timeout can occur after the remote side accepted a non-idempotent write, so a blind retry can create a duplicate.
Does the connector replace the native CRM record?No. Native clients, invoices and payments remain the operational source records. The connector records mappings, remote evidence and controlled reconciliation around them.
What should I include in a support case?Include the native record ID, remote ID if known, date/time, action, exact visible error and request/audit identifier. Never send client secrets, access tokens, refresh tokens or authorization headers.

Technical basis for this guidance

This guide was checked against the supplied module code paths: controllers/Sage_accounting_automation.php; models/Sage_accounting_automation_model.php; libraries/Sage_api_client.php; libraries/Sage_reconciliation_service.php; libraries/Sage_document_import_service.php; views/admin; install.php; docs/FEATURE_MATRIX.md. It documents shipped behaviour, validation, routes and evidence controls; it does not claim successful live provider network calls from offline inspection.

Controls, checks and common mistakes

  • Work in the intended tenant and remote accounting/business context.
  • Do not paste credentials, access tokens, refresh tokens or private keys into tickets or notes.
  • Do not bypass a missing mapping, validation error, permission gate, duplicate check or remote-verification requirement.
  • Do not repeat a non-idempotent write until you know whether the previous request reached the remote service.
  • Keep native record, remote evidence and audit/history state aligned before closing the task.
Provider and accounting boundaryThe integration fails closed when required mapping, remote identity, validation, concurrency or verification evidence is missing. Do not bypass a blocker by editing unrelated records or repeating an uncertain write.
Browse connected topics: Queue, exceptions and manual review Sage Accounting Automation Accounting & Bookkeeping
Recover a stale Sage processing job through the controlled queueClose a Sage exception only after verifying both systemsAccounting & Bookkeeping guides