remoteEaze

COB, reports, imports, or delivery problems

How to diagnose processing, reporting, and integration problems.

COB

Open the failed run and identify the first Failed step and Posting Exceptions. Check the frozen safety policy, pending approvals, due Forward-Dated Transactions, retro-accrual/schedule jobs, financial posting failures, and balance controls. Correct the source condition before retrying. A retry is only available for the failed canonical run on the current working date.

Reports and exports

Open Run History or the Export Job. Confirm Company, source, dates, Branches, filters, permissions, and failure message. Empty output can be a valid result of scope/filters. Expired or revoked artifacts must be regenerated from the source screen.

Imports

Open the Import Job and row results. Separate file/column validation failures from maker-checker status and commit-time business failures. Correct invalid rows at the source; do not authorize a job until warnings and intended row counts are understood.

Third-party delivery

Open the Delivery Log and use correlation/job IDs to match the Hook and remote system trace. Check Hook/System active and Authorized status, endpoint, method, authentication, timeout, mapping, External IDs, HTTP status, response, attempt, and next retry. Test Delivery sends a real request; use it only after confirming the destination is safe.

On this page