In connectAll many clarity artifacts trying to be linked to one Service Now artifact after granting the user read access to the planned_task_read table.
search cancel

In connectAll many clarity artifacts trying to be linked to one Service Now artifact after granting the user read access to the planned_task_read table.

book

Article ID: 403845

calendar_today

Updated On:

Products

ConnectAll SaaS

Issue/Introduction

Customer is seeing many clarity artefacts trying to be linked to one Service Now artifact after granting the user read access to the planned_task_read table. This occurred in the SAAS Prod env after changing to use Oauth Authentication.

Environment

3.8.x

Cause

DE171708

Resolution

Steps to Reproduce: 

  1. Create automation between Clarity and SNOW

  2. Change to use Oauth

  3. See Oauth Fail

  4. Token got updated and refreshed the connection

  5. The records started getting queued (but all the records fetched mapped to one record in SNOW)

  6. updated that one record incorrectly

Expected Results: 

  • No errors anymore in Oauth

Actual Results:

  • The records started getting queued (but all the records fetched mapped to one record in SNOW)