A connection goes offline when integrator.io can't reach the application. Flows and APIs that use an offline connection can't run their steps until the connection is back online.
integrator.io re-tests an offline connection automatically: first within about an hour, then after waits of 1, 2, 4, 8, 16, and 32 hours (roughly 2, 5, 10, 18, 35, and 67 hours after the connection went offline). It also refreshes tokens when the connection type supports it. If the last re-test, just under three days after the connection went offline, also fails, the connection stays offline until you fix it.
This article shows how to bring a connection back online, fix NetSuite authentication, and understand how offline connections affect APIs.
What takes a connection offline
A connection test sets the connection's status. Test connection in the connection settings, saving the connection, and the REST API's connection ping (GET /v1/connections/{id}/ping) all run the same test:
- If the test fails for any reason, the connection is marked offline, the flows that use it pause until a test passes, and the offline notification is sent.
- If the test passes, the connection is marked online.
integrator.io doesn't test online connections on its own. Its automatic re-tests cover only connections that are already offline. If a connection goes offline and comes back by itself, especially at regular times, something in your account tested it: a script that calls the ping on a schedule, or a user selecting Test connection.
Because every failed test marks the connection offline, a monitoring script that pings connections on a schedule turns every slow or refused response into an outage. To check a connection's status without testing it, read the connection's offline field instead. Reading it has no side effect.
Bring a connection back online
- Open your connection list. In an integration, select the Connections tab. To see every connection in your account, select Resources > Connections.
-
Find the offline connection, open its menu in the Actions column, and select Edit connection.
- Update the credentials or settings that changed, then select Save. If the connection uses OAuth, authorize it when prompted.
You don't need to wait for the next automatic re-test. Once the cause is fixed, for example the application is back or the credential has been replaced, select Test connection to bring the connection back online right away. Because the wait between automatic re-tests grows, a connection that has been offline for a day might not be re-tested for many hours.
Fix an offline NetSuite connection
If your NetSuite connection uses basic authentication, switch it to token-based authentication, which is more secure. See Change NetSuite Connection from Basic to Token.
-
In Edit connection, select Token Based Auth (Automatic) as the authentication type.
- If automatic setup doesn't work, select Token Based Auth (Manual) instead, and follow the steps in the manual token-based authentication guide (PDF, written for the Shopify integration app).
Troubleshoot NetSuite authentication errors
"Sorry, but we were not able to successfully authenticate your connection"
- Cause: Token-based authentication isn't enabled in your NetSuite account, so NetSuite rejects the login with status code 400 ("Invalid login attempt").
- Resolution: A NetSuite administrator must enable this feature. In NetSuite, go to Setup > Company > Enable Features, then select the SuiteCloud subtab. In the Manage Authentication section, check Token-based Authentication and accept the SuiteCloud Terms of Service. Select Save, then reauthorize the connection in integrator.io.
NetSuite returns the same "Invalid login attempt" message for several other reasons. These are more likely when a connection that worked before goes offline:
- Cause: The connection targets a sandbox that was refreshed. A sandbox refresh deletes every access token issued in the sandbox. Production tokens are not affected, and a production token never works in a sandbox.
- Resolution: Create a new token in the refreshed sandbox for the integrator.io application and enter it in the connection. See Perform a NetSuite sandbox refresh.
- Cause: The token was deleted, made inactive, or created for a different account or application.
- Resolution: Create a new token. Re-entering the same token values doesn't help.
- Cause: The user or role behind the token is inactive, or the role doesn't have the Log in using Access Tokens permission.
- Resolution: Fix the user or role in NetSuite, then create a new token for that user and role.
- Cause: The integrator.io integration record in NetSuite is Blocked.
- Resolution: In NetSuite, go to Setup > Integration > Manage Integrations, open the integrator.io integration record, and set its State to Enabled.
To find out which of these applies, open NetSuite's Login Audit Trail (Setup > Users/Roles > User Management > View Login Audit Trail) and add the Detail column. The failed login shows token_rejected, permission_denied, InvalidSignature, or consumer_key_refused.
unexpected_error:request_aborted
- Cause: The connection test got no answer from the application within integrator.io's limit of about six minutes. On an offline alert, this error isn't about your credentials.
- Resolution: Reauthorizing doesn't help. Wait until the application is responding again, then select Test connection to bring the connection back online.
netsuite_wsdl_tba_mandatory
- Cause: The connection has no token. When this error appears right after you reauthorize the connection, the old token was revoked and the new authorization didn't complete.
- Resolution: Complete the authorization. Don't change the WSDL version or the authentication type.
Offline connections in APIs
When a connection an API uses goes offline, the API either fails immediately with HTTP 500 or waits and fails with HTTP 504 when the API times out. The API's Immediate error for offline connections setting controls which one happens. See Create and manage APIs using API builder.