{"id":119,"date":"2026-09-28T09:00:00","date_gmt":"2026-09-28T07:00:00","guid":{"rendered":"https:\/\/yindle.com\/?p=119"},"modified":"2026-09-28T09:00:00","modified_gmt":"2026-09-28T07:00:00","slug":"afas-record-vergrendeld-herstellen","status":"publish","type":"post","link":"https:\/\/yindle.com\/en\/safely-recovering-a-locked-afas-record\/","title":{"rendered":"Safely recovering a locked AFAS record"},"content":{"rendered":"

Treat a locked AFAS record as a temporary business obstacle, not a reason to keep writing indefinitely. Pause the specific provider step, show which record is in use, and decide based on duration and impact whether to try later, have a user release it or resolve it manually. Other independent orders may continue.<\/p>\n

Why rapid retries make the problem worse<\/h2>\n

A record may be in use by an employee, batch or another process. Ten retries within one minute do not shorten the lock, but do fill queues and notifications. Even riskier is a fallback that tries to create a new record after an update error: this turns a temporary lock into a duplicate debtor or order problem.<\/p>\n

Classify the response separately from validation errors and permanent configuration errors. Retain the destination identity, last response and time of the first block. A worker may reschedule the task with a bounded delay, but must involve an owner after an agreed limit. This lets Connect<\/a> continue working without bombarding a locked record.<\/p>\n

Waiting, recovery and escalation ladder<\/h2>\n
\n\n\n\n\n\n\n\n\n\n
Stage<\/th>\nIndication<\/th>\nAction<\/th>\n<\/tr>\n<\/thead>\n
Wait briefly<\/td>\nFirst lock, no urgency<\/td>\nDelayed retry with an increasing interval<\/td>\n<\/tr>\n
Check<\/td>\nLock keeps recurring<\/td>\nVerify the destination record, permissions and active AFAS session<\/td>\n<\/tr>\n
Ownership<\/td>\nOrder is blocking fulfilment<\/td>\nTask assigned to a specific administrator with context<\/td>\n<\/tr>\n
Resolve manually<\/td>\nLock or conflict is structural<\/td>\nCorrect source or destination and record the decision<\/td>\n<\/tr>\n
Run again<\/td>\nBlock demonstrably removed<\/td>\nRepeat only the stalled step<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

Do not use a universal time limit. An address update for tomorrow's delivery may deserve earlier escalation than non-critical profile enrichment. Record the business deadline and dependent steps alongside technical age.<\/p>\n

Fictional example: debtor record open in accounting<\/h2>\n

Fictional example: the accounting team at coffee shop Branderij Noord has a debtor record open in AFAS while order 7721 attempts an address correction. AFAS reports that the record is locked. The integration retains the debtor number, pauses only the address step and lets other orders process normally.<\/p>\n

After two delayed attempts, the lock is still active and the delivery cutoff is approaching. Desk shows the situation with \u201cfinancial administration\u201d as owner, the order deadline and instructions to release the record after checking. The administrator closes the edit, after which only the address step runs again. No new debtor is created and the original order flow remains traceable. The example is fictional and makes no claim about the exact lock duration in any particular AFAS setup.<\/p>\n

What an employee needs to see<\/h2>\n