Some PDIs are currently unavailable, and PDI actions are paused. View the latest updates here. Read More

Remote Instance Spoke – “Unable to load dynamic inputs (sn_now_remote_spk.list_remote_tables) ”

gayatri23
Tera Contributor

Hi Everyone,

 

I am integrating two ServiceNow instances using the Remote Instance Spoke.

 

Setup:

 

* Using the default parent connection alias

* OAuth 2.0 Authorization Code grant

* Token generation successful

* Token is active and not expired

* Redirect URL points to local instance

* Auth Scopes: rest_api, sn_table_read, sn_table_write

 

Issue:

 

When configuring the “Create Remote Record” action in Flow Designer, selecting the Remote Table results in:

 

> Unable to load dynamic inputs (sn_now_remote_spk.list_remote_tables)

> Bad Request – Error occurred while fetching remote tables

 

It appears the spoke cannot fetch table metadata from the target instance.

Would appreciate any troubleshooting suggestions.

4 REPLIES 4

Tanushree Maiti
Tera Patron

Hi  ,

 

It seems configuration wise, something is missing at your end. Go to flow execution log and check what exact error it is throwing.

 

Check these two post/article- if it helps you.

https://www.servicenow.com/community/developer-forum/remote-instance-spoke-dynamic-error-on-field-se...

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2239511

 

 

 

 

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

akash05sde
Giga Contributor

Hello
Have you found a solution? I'm experiencing the same issue.

akash05sde
Giga Contributor

Hello
Have you found a solution? I'm experiencing the same issue.

When I access the 'Create Remote Record' action from Flow Designer and test its REST step separately, I encounter the following e error:

 

{"message":"User Not Authorized","detail":"Access to unscoped api is not allowed"]

 

This KB Article "https://support.servicenow.com/kb?id=kb_article_view&sysparm_article-KB2731346" provides the resolution for the same.

 

Steps followed -

 

I located the Scope Restriction field in Remote instance Application registry record I created to establish the connection and changed the value from Securely Scoped to Broadly Scoped.

 

Please accept the solution if it resolves your issue. Thank you!