Link Unfurling Flow Error

Usha16
Kilo Explorer

Hello Everyone,

I have query on link unfurling flow.

Flow got an error during execution:

Flow Designer: Operation(Link Unfurling .a1a21ed6c3c3201032480d1eb540ddd2.1d6256d6c3c3201032480d1eb540dd22) failed with error: com.snc.process_flow.exception.OpException: Unexpected behavior from remote host: Relative redirect location '/auth_redirect.do?sysparm_stack=no&sysparm_url=https%3A%2F%2Fsts2.*******.com%2Fadfs%2Fls%2F%3FSAMLRequest%3DlVLJTsMwEP2VyPesNE1rNZVCK0QllogUDtyMM2ktOXbwOAX%252BntQNAg4gOPhiv23meYGslUlHi97u1R0894DWe22lQnp6yUlvFNUMBVLFWkBqOa2K6yuaBBHtjLaaa0m8AhGMFVqttMK%252BBVOBOQgO93dXOdlb2yENwxasFA0MrDrA07uv9EvAdRsqdujYDoJaE289pBCKHeU%252ByWgxCUYFx2B1g6HEkHgX2nBwI%252BSkYRKBeJt1TqqbVVPPs%252BxsOFOeTTMWpTCdw4xHU57M0kkWDUAsGaI4wCcVsYeNQsuUzUkSJYkfxX6SbuOUphMaz4PJWfRIvHIc%252FlyoWqjd75t6OoGQXm63pV%252FeVlsncBA1mJsB%252Ff8lPYBBt6BBniwXri7qspuvDf4ei33URpZ%252F8F%252BEX11Gz44e82%252FWpZaCv3mFlPplZYDZYSZrenD1tMz%252BHCQOYncjar9xUNor7ICLRkBNwuVo%252B%252F2XLt8B%26RelayState%3Dhttps%253A%252F%252F*************.service-now.com%252Fasset%252Freports.do' not allowed

1. From where is the link unfurling subflow getting called?

2. Why do we get this error, service-now.com is already present in sys_cs_hostname_allow_list_list?

KIndly help me on this.

2 REPLIES 2

Prasad Pagar
Mega Sage

Hi Usha,

Check it under Flow Executions from Navigator -> Flow Designer

Check trigger for Flow and rectify.

Thank you
Prasad

Joseph Warner
Tera Guru

One option is to avoid the link unfurling error by disabling link unfurling.

  • Select "Global" in the Application Picker
  • sys_properties.list
  • New
    • Suffix: com.glide.cs.enable_link_unfurling
    • Application: Global            (scoped application will not work)
    • Description: Enable/disable link unfurling (previewing).
    • Type: true | false
    • Value: false
  • Click on "Update"

The link unfurling error should no longer appear since link unfurling has been disabled. Caveat: link unfurling is now disabled for the entire instance.

 

I tested creating a scoped system property for this on my PDI which is on Rome patch 5-12-15-2021 (glide-rome-06-23-2021__patch5-12-15-2021) but it had no effect, while setting a global system property was effective. The virtual agent topic in question WAS in the scoped application. It is possible creating a system property in Studio might work.