This page covers various errors that may occur when using the InterAction+™ Connector for Microsoft® Power Automate®, such as Unauthorized, Bad Request, Internal Server, and 429 Rate Limit errors, detailing their common causes and proposed resolutions. Ensure that you verify your inputs, follow the account switching process correctly, and adhere to the defined rate limits to minimize interruptions and unexpected behavior.
If you need assistance or have any questions, our Customer Support team is here to help. Please reach out to us by emailing support@interaction.com.
Unauthorized Error
-
Click on the Connections tab on the side panel.
- Search for an InterAction connection from the list of connections available.
- Click on the Switch Account option. Allow the custom connector access when a pop-up window appears.
- On the page, enter your username and click the SAVE button to refresh the connection.
Bad Request Error
The HTTP 400 Bad Request status code indicates that the server cannot process the request due to a client error.
- Common Causes: These include malformed request syntax, invalid request message framing, or invalid input.
- Resolution: Correct inputs and resubmit the job.
Internal Server Error
The HTTP 500 Internal Server Error status code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.
- Common Causes: Possible cause is Interaction+ Public API server issue.
- Resolution: It might be due to server maintenance which will resolve automatically once server is up. If it does not go away contact InterAction+ Support Team.
429 Rate Limit
The HTTP 429 stands for Too Many Requests error that tells the client application to stop sending requests because they simply don’t have enough resources to accept it at this time.
- Common Causes: Too many requests in particular timeframe.
-
Resolution: Check for Retry-After header in response and retry after specified time. The applied limits are as follows:
- 5 requests per second
- 100 requests per minute, divided into six equal segments using a Sliding Window algorithm to handle traffic bursts efficiently (~ 16 requests every 10 seconds).
- 6,000 requests per hour (Fixed limit)
- 18,000 requests per day (Fixed limit)
- For further details on Rate Limit please visit InterAction+ API specifications: Rate Limiting and Complexity Analysis – InterAction API
Other Known Issues
- Sometimes you may receive unexpected error messages in the response due to invalid inputs (for example, an incorrect date or GUID format). Be sure to verify your inputs and resubmit the job.
- When using the Update Person Contact action to update the company name, the current company may be unlinked and the person's Business Address cleared.
LexisNexis, InterAction and the Knowledge Burst logo are registered trademarks and InterAction+ is a trademark of RELX Inc. Microsoft and Power Automate are registered trademarks of the Microsoft group of companies.