Conflict errors, empty ERP System ID dropdowns, rejected validity dates, and lifecycle messages that never arrive all have known causes. Match the symptom to its fix.

Conflict error on inbound endpoint creation

If endpoint creation returns a conflict error, your participant identifier may have already been written to the SMP before the API returned the error. Check whether the endpoint exists before retrying. Creating a duplicate endpoint for an already-registered participant identifier results in a permanent conflict.

ERP System ID not showing in the dropdown

Only ERP System IDs you create manually in Compliance Network appear in the Network Settings dropdown. Auto-provisioned defaults aren't synchronized to Network Services and can't be used for endpoint configuration. Create a new ERP System ID manually. See Set up account.

Same-day validity date rejected

Production endpoints don't accept a validity period start date of today. Use at least tomorrow's date and retry.

Lifecycle communications not routing after endpoint creation

If you've created an endpoint and configured ERP System Communications but lifecycle notifications (MLR, eMLR) aren't arriving, check that your Lifecycle communication has a plugin selected. The platform returns success when you create a Lifecycle communication without a plugin, but lifecycle messages won't route to your system. Return to ERP System Communications, open the Lifecycle entry, and select a plugin.