Maybe this will help point you in the right direction.
First, are you using the default Business Central APIs or a custom API integration for your CRM-to-BC sync?
If it’s a custom integration, then yes — you can handle this scenario by adding error handling logic in your API processing code. Instead of letting a single record failure stop the entire Job Queue or transaction, you can:
Wrap your record processing in a try…catch block (if using AL or external integration logic).
Log the error message and the failed record to a custom error log table or external system.
Continue processing the next record without rolling back the whole batch.
This will prevent auto-rollback and give you better traceability for failed records.
Unfortunately, BC doesn’t support this behavior out-of-the-box for batch API processing — it needs to be handled in your integration layer.
Mark this as the verified answer if it helps. Let me know if you want an AL code example
