Resolve sync failures caused by “Record Locked by Workflow”
When you sync Re-Leased with NetSuite and see this error, a custom NetSuite workflow is blocking record updates made through the API. The quick fix is to update or remove the lock in that workflow so Create and Edit actions can proceed. Below, you’ll confirm the cause and choose the right fix.
Understand the error
The “Record Locked by Workflow” error means a NetSuite workflow actively stops record creation or edits made by integrations. This control helps manage changes, but it also blocks Re-Leased from syncing important data if the lock includes the RESTlet context.
View the error message
Here is a common message you might see in Re-Leased during a sync:
Contextual note: This banner appears on the sync log or error details screen when NetSuite blocks the update.
Review a typical locking rule
Workflows in NetSuite can lock a record based on state, event type, and context. If the lock applies to Create or Edit and includes RESTlet, the API sync from Re-Leased will fail.
- State: Locked
- Event types: Create or Edit
- Context: Includes RESTlet
Contextual note: This screenshot shows a workflow state configured to lock the record when Create or Edit runs in the RESTlet context.
Fix workflow settings that block API updates
Pick the option that fits how you use the workflow. If locking is no longer needed, turn it off or remove it. If locking is still useful, adjust it so RESTlet updates from Re-Leased are not blocked.
Deactivate the locking rule
Use this when the lock is not needed right now.
- Locate the workflow action or rule that locks the record.
- Deactivate that specific action or rule.
- Save the workflow and re-run the sync from Re-Leased.
Only deactivate the lock when it is no longer necessary for your current process.
Remove the locking action
Use this when the lock is not needed for any process.
- Find the locking action in the workflow.
- Delete the locking action.
- Save the workflow and re-run the sync from Re-Leased.
Removing the lock keeps the record editable and prevents the workflow from blocking future updates.
Adjust the lock for API sync
Use this when you still need locking for some processes, but want API updates to go through.
- Edit the locking action in the workflow.
- Remove the Create and Edit event types from the locking action.
- Remove the RESTlet context so API-based syncing is not affected.
- Save the workflow and re-run the sync from Re-Leased.
Keep the lock for manual work if needed, but exclude RESTlet so integration updates succeed.
Prevent repeat sync errors caused by workflow locks
Make sure your NetSuite workflows do not lock records during Create or Edit events when the RESTlet context applies. This setup allows Re-Leased to sync without errors while keeping any other lock behavior you still need.