When syncing Re-Leased with NetSuite, a "Record Locked by Workflow" error means a custom NetSuite workflow is blocking record creation or edits made through the API. The fix is to update the workflow so it no longer locks records when the RESTlet context applies.
Understanding the Error
NetSuite workflows can lock records based on state, event type, and context. If a workflow locks records during Create or Edit events when the RESTlet context is active, Re-Leased's API sync will fail.
Option 1: Deactivate the Locking Rule
Use this when the lock is temporarily not needed.
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.
Option 2: Remove the Locking Action
Use this when the lock is no longer needed for any process.
Find the locking action in the workflow.
Delete the locking action.
Save the workflow and re-run the sync.
Option 3: Adjust the Lock to Allow API Sync
Use this when you still need locking for manual processes but want API updates to go through.
Edit the locking action in the workflow.
Remove Create and Edit from the event types.
Remove RESTlet from the context so API-based syncing is unaffected.
Save the workflow and re-run the sync.
Note: Ensure your NetSuite workflows do not lock records during Create or Edit events when the RESTlet context applies. This allows Re-Leased to sync without errors while preserving any other lock behaviour you need.