Can't trace errors from log explorer

RaresZynk — Tue, 06 Feb 2024 14:02:27 GMT

Hello,

We have a project for google home and we found some errors that we can't trace in our own logs on the server. Can anybody provide some more information on what is happening?

{"@type":"type.googleapis.com/google.identity.accountlinking.type.AccountLinkingError", "errorReason":"Could not refresh token, 3P returned error:invalid_grant", "request":{…}, "response":{…}, "sessionId":2.54139613E8, "step":"REFRESH_ACCESS_TOKEN"} { "insertId": "a0zpsc47d", "jsonPayload": { "step": "REFRESH_ACCESS_TOKEN", "request": { "headers": { "Authorization": "Basic Base64EncodedREDACTEDClientIdAndSecret" }, "uri": "https://assistant.homplex.com/oauth2/token", "body": "grant_type=refresh_token&refresh_token=REDACTED_VALUE", "method": "POST" }, "response": { "status": 400, "body": "{\"error\":\"invalid_grant\"}" }, "sessionId": 254139613, "errorReason": "Could not refresh token, 3P returned error:invalid_grant", "@type": "type.googleapis.com/google.identity.accountlinking.type.AccountLinkingError" }, "resource": { "type": "assistant_action_project", "labels": { "project_id": "homplex-92698" } }, "timestamp": "2024-02-05T06:52:01.336Z", "severity": "ERROR", "logName": "projects/homplex-92698/logs/accountlinking-pa.googleapis.com%2Ferror", "receiveTimestamp": "2024-02-05T06:52:01.943664478Z" }

Not sure if they're normal errors regarding expiration of the token, or if there's something that we are doing wrong.

Thank you.

Re: Can't trace errors from log explorer

sipriyadarshi — Thu, 08 Feb 2024 17:28:09 GMT

Hello @RaresZynk ,

Looking at the screenshots shared by you we notice you are receiving “GAL_UNLINKED_BY_3P”, “Agent responded empty JSON”, “EXECUTION_GAL_UNLINKED_BY_3P” and “GAL_NOT_FOUND”.
The following could be the reason for getting the above mentioned respective errors :

“GAL_UNLINKED_BY_3P” : When we are trying to refresh the token, if the partner returns an error code through token request we consider the account as unlinked. (403 or 404) .
“Agent responded by empty json” : When we send a query or request we get a blank or empty response from the server .
“GAL_NOT_FOUND” : account linking error

Google makes calls to your OAuth2 endpoints during the account linking process. These calls can fail for different reasons. Detailed information is logged for these errors and you can monitor them in the Logs Explorer page of your cloud console project.
Google Cloud provides you the tools to monitor the reliability of your projects with Google Cloud Monitoring and debug issues with Google Cloud Logging error logs. Whenever a failure happens when fulfilling user intents, Google Home Analytics pipeline records that failure on your metrics, and publishes an error log in your project logs.
You can find more information about Monitoring Errors, Platform Error Codes and Search logs here.

topic Can't trace errors from log explorer in Smart Home Developer Forum

Can't trace errors from log explorer

Re: Can't trace errors from log explorer