Hi @Candace Low,
I'm assuming that since this was posted as an FME Desktop question, it's happening on FME Workbench?
Just want to confirm, because the article goes through steps for both FME Workbench and FME Server.
By default, ArcGIS Enterprise Portal refresh tokens expire after 14 days. The refresh token is used to obtain a new access token, which will usually expire after a couple of hours. But it's possible that the Portal you are connecting to has been configured for them to expire sooner.
Either way, if the workspace is not run for a period of time, a new refresh token isn't obtained and it expires. You can obtain a new one by going to Tools > FME Options > Web Connections and then right-clicking the connecting and choosing 'Reauthenticate...'. You can also avoid this by manually running a simple workspace (for example, a single reader) that just connects to the portal every few days. You can take it a step further by scheduling the workspace to run every few days using Windows Task Scheduler. If you're on Linux, I believe you can use CRON to do this.
Hi @Candace Low,
I'm assuming that since this was posted as an FME Desktop question, it's happening on FME Workbench?
Just want to confirm, because the article goes through steps for both FME Workbench and FME Server.
By default, ArcGIS Enterprise Portal refresh tokens expire after 14 days. The refresh token is used to obtain a new access token, which will usually expire after a couple of hours. But it's possible that the Portal you are connecting to has been configured for them to expire sooner.
Either way, if the workspace is not run for a period of time, a new refresh token isn't obtained and it expires. You can obtain a new one by going to Tools > FME Options > Web Connections and then right-clicking the connecting and choosing 'Reauthenticate...'. You can also avoid this by manually running a simple workspace (for example, a single reader) that just connects to the portal every few days. You can take it a step further by scheduling the workspace to run every few days using Windows Task Scheduler. If you're on Linux, I believe you can use CRON to do this.
I am having the exact same issue. Yes, this is in Workbench. Any help would be very much appreciated.
I'm seeing this behavior as well on several of my AGOL portals I connect to (not all of them). I can go into Web Connections > Manage Services and Test each one of my connections and they authenticate fine (on Form and Flow). However, simply trying to add a simple reader to my desktop results in the Type 4, Number 1 Error, Failed to get auth query string. Not sure what is going on...
Chad