We’re seeing a small but recurring UX gap in our Moveworks → UKG plugin flow and wanted to check if others have solved this or if there’s a recommended pattern.
Current behavior
-
User asks Moveworks to perform an action (example: approve timecard).
-
Plugin detects expired/invalid OAuth token for UKG.
-
Moveworks prompts the user to re-authorize via an auth link.
-
After successful authorization, the user must explicitly type something like “retry approve timecard” to continue.
-
Only then does the plugin re-execute the original action.
From the user’s point of view, it feels broken or incomplete — they believe the task should continue automatically once access is granted.
Expected / desired behavior
Once the user completes authorization successfully:
-
Moveworks should automatically resume the original plugin execution
-
The user should not be required to type a manual “retry” command
-
The experience should feel like a single continuous flow, not two separate conversations
Questions for the community / Moveworks team
-
Is there a supported way to persist the original intent and automatically re-trigger the plugin after OAuth completes?
-
Are there best practices for handling token refresh / re-auth flows without requiring explicit user retries?
-
Is this a current platform limitation, or something that can be configured at the plugin or workflow level?
Would love to hear if anyone has implemented a smoother post-authorization continuation pattern or if this is already on the roadmap.
Thanks!
