Overview

GoMembers 4gov DiLOG includes two utilities that are sometimes confused because both relate to recovering from an unexpected state: Error Recovery and Reset for Correction. Using the wrong one can leave the system in an incorrect status or disrupt processing.

The key difference is simple: Reset for Correction cancels a successfully completed Transaction Edit when you decide not to proceed to Update Ledgers. Error Recovery is reserved for situations where a multi-step process ended abnormally and left the system in an unexpected status.

An important detail unique to DiLOG: its normal steady-state status is GOOD, not ALLCLEAR. Other 4gov modules such as CAPPS and Cash Receipts use ALLCLEAR as their normal status, so do not assume DiLOG should be returned to ALLCLEAR.

In This Article

• DiLOG System Statuses
• Reset for Correction
• Error Recovery
• Quick Reference: Which Tool to Use
• FAQ

DiLOG System Statuses

You can view the current system status at any time by navigating to Financials > DiLOG Accounting > Utilities > Quick System Status.

GOOD

The normal DiLOG steady-state status. When DiLOG shows GOOD, normal processing can proceed. This is the status to return to when any processing issue has been resolved.

RUNEDT

DiLOG moves to RUNEDT after a Transaction Edit completes successfully. The system is waiting for your next decision: either continue with Update Ledgers to post the transactions, or use Reset for Correction to cancel the edit and return to GOOD.

RUNUPD

DiLOG moves to RUNUPD when Update Ledgers is actively running. If that process ends abnormally and the system remains at RUNUPD, Error Recovery is the correct tool to restore the system to its prior state.

ALLCLEAR

ALLCLEAR is the normal status for other 4gov modules such as CAPPS and Cash Receipts — not DiLOG. Do not use ALLCLEAR as a target status when resolving issues in DiLOG.

Reset for Correction

Reset for Correction is the correct action when a Transaction Edit has completed normally and you choose not to continue with Update Ledgers. It cancels the edit state and returns DiLOG from RUNEDT back to GOOD so normal processing can resume.

When to Use It

• Transaction Edit finished successfully, but you want to make corrections before posting.
• Transaction Edit finished successfully, but you have decided not to post at this time.

Steps

1. Navigate to Financials > DiLOG Accounting > Transaction Processing Menu.
2. Select Reset for Correction.
3. Confirm. DiLOG returns to status GOOD.

After this, the transactions in the input file remain unchanged and can be edited or re-submitted for a new edit run.

When Not to Use It

Do not use Reset for Correction when processing ended abnormally or the system is stuck in RUNUPD. In that case, use Error Recovery instead.

Error Recovery

Error Recovery is used when a multi-step DiLOG process ends abnormally — for example due to a hardware or software failure — and the system is left in a processing status it cannot exit on its own. It restores the system to the status that existed immediately before the failed process began.

Because DiLOG may process inputs from feeder systems external to itself, recovering to an intermediate status (such as RUNEDT) is intentional and correct — it means the edit data is preserved and only the failed update step needs to be re-run.

When to Use It

• Update Ledgers failed mid-run and DiLOG is stuck at RUNUPD.
• Another multi-step process ended abnormally and the system did not return to its expected status.

Steps

1. Navigate to Financials > DiLOG Accounting > Administrative Functions > Utilities > Error Recovery.
2. Confirm the recovery action.
3. DiLOG restores the system to the status it held before the failed process started.

For example: if Update Ledgers failed and left status at RUNUPD, Error Recovery returns it to RUNEDT. From there, you can either re-run Update Ledgers or use Reset for Correction to cancel the edit entirely.

When Not to Use It

• Do not run Error Recovery after a Transaction Edit that completed normally — use Reset for Correction instead.
• Do not run Error Recovery to clear a temporary record lock. If users were blocked from a menu due to a record-lock conflict and the issue has since cleared on its own, no recovery action is needed.

Quick Reference: Which Tool to Use

Situation	Current Status	Correct Action	Status After
Transaction Edit finished; you do not want to post	RUNEDT	Reset for Correction	GOOD
Update Ledgers failed or was interrupted	RUNUPD	Error Recovery	RUNEDT
System is normal and ready for processing	GOOD	No action needed	GOOD
Temporary record lock resolved by itself	GOOD (after lock clears)	No action needed	GOOD

FAQ

Q1: Transaction Edit completed successfully but I want to make corrections. What should I do?
A1: Select Reset for Correction from the Transaction Processing Menu. This cancels the edit state, returns DiLOG to status GOOD, and leaves your transactions available for editing and re-submission.

Q2: Update Ledgers failed partway through and DiLOG is showing status RUNUPD. What should I do?
A2: Run Error Recovery from Administrative Functions > Utilities. This returns DiLOG to the status it held before the update started — typically RUNEDT. From there, you can re-run Update Ledgers or use Reset for Correction to cancel the edit.

Q3: Why does DiLOG use GOOD instead of ALLCLEAR as its normal status?
A3: DiLOG is designed to process inputs from both internal entry and external feeder systems. Its processing flow is built around distinct edit and update phases, each with their own status values. GOOD indicates the system is at rest with no pending edit or update in progress. ALLCLEAR is used by other 4gov modules — such as CAPPS and Cash Receipts — which have a different processing model.

Q4: After Error Recovery, DiLOG is at RUNEDT instead of GOOD. Is that correct?
A4: Yes. Error Recovery restores the status to where the system was before the failed process began. If Update Ledgers failed, the system was in RUNEDT before the update started, so that is the correct restored status. From RUNEDT you can proceed to re-run Update Ledgers or use Reset for Correction to return to GOOD.