Before Arcoro reads or writes a single record from Acumatica, the connector has to sign in and confirm it is pointed at the right company. That sign-in and check happens once per entity, before any employee or lookup data is processed. If the credentials are wrong, or the connector is pointed at a tenant that does not match those credentials, the whole sync run stops immediately with nothing synced.
A fourth message in this family, the gateway timeout, is different. It means Acumatica itself did not respond to a request in time. It is not a credential problem, and depending on whether it happens on a read or a write, it may not stop anything at all.
Error Messages
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| Acumatica Provider failed to authenticate. Please verify the connector properties and try again. If the problem persists contact Arcoro support. | Read and write | The connector could not obtain a sign-in token from Acumatica during setup, before any entity is processed. This happens when Acumatica rejects the supplied username, password, API Client Id, or API Client Secret, or when the sign-in request itself fails without a usable response. | Sync stopped. The entire run fails before any record is read or written. | Verify the four Acumatica connector credential fields, then re-enter and re-save them. |
| The credentials supplied are for use with the tenant '[tenant name]'. Please add this to the Tenant setting of the connector and try again. | Read and write | Sign-in succeeded, but the connector's Tenant setting is blank and the tenant check failed. The bracketed tenant name is read directly from the API Client Id credential (the part after the @ symbol). | Sync stopped. The entire run fails before any record is read or written. | Copy the tenant name out of the message and enter it in the connector's Tenant setting. |
| The tenant '[configured tenant]' either does not exist or is not properly configured for access with the supplied credentials. The credentials suggest trying '[client tenant]' as the tenant. Please verify the tenant information in Acumatica and try again. | Read and write | Sign-in succeeded, the connector's Tenant setting already has a value, but the tenant check still failed. The first bracketed value is whatever Tenant is currently configured on the connector. The second bracketed value is read directly from the API Client Id credential (the part after the @ symbol). | Sync stopped. The entire run fails before any record is read or written. | Replace the connector's Tenant setting with the second (suggested) tenant name from the message, unless you confirm that value is wrong for your setup. |
| The request timed out in Acumatica. | Read and write | Acumatica returned a gateway timeout (HTTP 504) on a request. Can happen on any entity, on any individual read or write call. | Varies. On a write (Employee only), the message is logged against that one employee record and that record is skipped; the sync continues with the next employee. On a read (any entity), this message is not written to the entity's error list at all; the call simply returns no data and the read continues with whatever it already had, so a timeout here can reduce record counts without any visible error. | Retry the sync. This is a passthrough condition from Acumatica, not a setting to change. |
Confirming the Error
- Open the sync execution for the run reported in the Sync History screen.
- Find the step for the Acumatica connector and open it to see the entities included in that run.
- Check the run's overall status first. For the authentication and tenant messages, the whole run shows as failed, and every entity in that run shows zero for Errors, Warnings, Information, Added, Updated, and Unchanged, because none of them were ever reached. The message itself appears as a run-level Failure, not as an error against any specific entity row, so do not expect to find it by opening an entity's error list.
- For the gateway timeout on a write, open the Employee entity row for that run and check its Errors count. The message appears against the specific employee record whose save call timed out; other employees in the same run can still show normal Added, Updated, or Unchanged counts.
- For the gateway timeout on a read, there may be nothing to find in the Errors column at all. If you see fewer records than expected with no visible error, a silent read timeout is a possibility worth asking about, alongside other causes.
- Match on the fixed wording of the message (for example "Please add this to the Tenant setting of the connector"), not on the tenant name or other values inside the quotes, since those are specific to the your data.
- The same generic authentication message can also appear as the Message on a failed connector connection test, separately from any sync run. Confirm whether you are looking at a connection test result or a sync run before proceeding, since the two are different surfaces.
Resolving the Error
Authentication Failed
- In Arcoro, open the Acumatica connector's settings.
- Confirm the UserName, Password, API Client Id, and API Client Secret fields are all filled in and match what you have configured for API access in your Acumatica instance.
- If any value looks wrong, confirm the correct value from your Acumatica instance and update it in Arcoro.
- Save the connector and retry the sync.
- If the same message still appears after credentials are confirmed correct, escalate.
Tenant Setting is Blank
- Read the tenant name out of the message text.
- In Arcoro, open the Acumatica connector's settings and enter that tenant name in the Tenant setting.
- Save the connector and retry the sync.
Tenant and Credentials Do Not Match
- Read the second (suggested) tenant name out of the message text.
- In Arcoro, open the Acumatica connector's settings and replace the Tenant setting with that suggested value.
- If the suggested tenant is not correct for your setup, verify in your Acumatica instance which tenant your API access user and API client are actually assigned to, since the credentials and the connector's Tenant setting must refer to the same tenant.
- Save the connector and retry the sync.
- If this message appeared right after a period when you noticed Acumatica was slow or unreachable, have them retry once before changing any settings, since a timeout during the tenant check can produce this same message.
Gateway Timeout
- Retry the sync. No connector setting change is expected to resolve this.
- If it recurs across multiple attempts, escalate, since this indicates a persistent responsiveness problem in the your Acumatica instance.
To confirm any of the above fixes worked, run the sync again and check that the run completes without a Failure, and that the Acumatica entities show Added, Updated, or Unchanged counts instead of remaining at zero.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The authentication message persists after you confirmed all four credential fields are correct in both Arcoro and Acumatica.
- A tenant message persists after the Tenant setting has been updated to the suggested value, and you confirm that the value is correct for your Acumatica environment.
- The gateway timeout message recurs across repeated retries. This message is a passthrough from your own Acumatica instance being slow or unresponsive, not a credential or configuration problem, so treat repeated occurrences as a target-system availability issue rather than something a settings change will fix.
- You notice missing or short record counts on an Acumatica read with no visible error anywhere in the sync log, which may indicate a silent read-side timeout that tier 1 cannot confirm from the log alone.