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.
3.8.x
DE171708
Steps to Reproduce:
Create automation between Clarity and SNOW
Change to use Oauth
See Oauth Fail
Token got updated and refreshed the connection
The records started getting queued (but all the records fetched mapped to one record in SNOW)
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)