Overview
Sometimes a workflow continues to fail even after a new credential is created and verified.
This usually happens because the destination or workflow is still pointing to an older credential, not the newly created one.
This article explains why this happens and how to fix it.
Symptoms
You may see one or more of the following:
Orchestration group fails with a credential-related error
Error message mentions an expired or invalid token
A new credential was recently created, but failures continue
Credential connection tests succeed, but workflows still fail
Manual retries do not resolve the issue
Common Error Message
You may encounter an error similar to:
Refresh token has expired. Please create a new credential.
This indicates that the workflow is still using an expired credential.
Why This Happens
Creating a new credential does not automatically update existing destinations or workflows.
Common causes include:
A destination still references an older credential
The workflow was not updated after the new credential was created
UI changes make it easy to miss updating the destination
Multiple credentials exist with similar names
As a result, workflows continue to use the expired credential and fail.
Solution: Update the Destination to Use the New Credential
To resolve this issue, you must explicitly update the destination or workflow to use the new credential.
Steps to Fix
Go to Settings → Destinations
Open the destination used by the failing workflow
Locate the Credential setting
Select the newly created credential
Save the changes
Re-run the orchestration or workflow
Once updated, the workflow should complete successfully.
Validation After Fix
After updating the credential:
Run a manual orchestration to confirm success
Check that no credential-related errors appear
Retry any previously failed runs if needed
If the test run succeeds, the issue is resolved.
Best Practices
Always update destinations after creating a new credential
Use clear naming for credentials to avoid confusion
After credential changes, run a test orchestration
Review workflows when tokens are rotated or refreshed
Keep old credentials disabled or removed once replaced
Summary
Creating a new credential alone is not enough to fix credential-related workflow failures.
The destination or workflow must be explicitly updated to use the new credential.
Once the correct credential is selected and saved, workflows will resume normally.
Applies To
Orchestration workflows
Destinations using external platforms
Credential management
Token-based integrations