Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed /fac requests #558

Closed
alexgurr opened this issue Apr 7, 2022 · 5 comments
Closed

Failed /fac requests #558

alexgurr opened this issue Apr 7, 2022 · 5 comments

Comments

@alexgurr
Copy link

alexgurr commented Apr 7, 2022

Hi,

We've been observing this for a while from connect streams lib. These requests are not triggered by our application but somewhere internally in the library.

We see a collection (7) failed POST requests to https://ourinstance.awsapps.com/connect/ccp-v2/fac/. This seems to only happen around the time the CCP is initialised/authed. https://puu.sh/ITfJ9/ec3ab2f7f7.png

Any ideas? There doesn't seem to be any observed impact.

This is the error response:

{"status":400,"message":"Invalid input!"}

Payload (string values obfuscated):

accountId: "ID"
featureName: "ID"
instanceId: "ID"
@CiscoKidxx
Copy link

Experiencing same behavior

@DanielHuelse
Copy link

I also see this error in our applications.

@martin-greenberg
Copy link
Contributor

This behavior is expected and can be ignored.

@florin05
Copy link

@martin-greenberg , I would disagree that the behavior of seeing many errors in the browser console is expected. We are embedding the CCP in our application and getting these errors is impacting our testing where we check to see if any errors are thrown, we don't want to say that some errors are expected and some are not. Our rule is to have no errors in the console log.

@bml1g12
Copy link

bml1g12 commented Nov 1, 2023

@martin-greenberg I have to agree with @florin05 , errors are by definition not expected...if it's expected, then it should not be an info or warning level log, and for this issue to be resolved, there should be at least an official recommendation on how to silence it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants