How to fix it

  1. Navigate to System Applications > Studio and select the scope containing your flow.
  2. Open your flow and click on the failing spoke action step to view its configuration.
  3. In the spoke action properties, locate the Connection or Credential field and note the referenced alias name.
  4. Navigate to Connections & Credentials > Credentials and search for the credential alias from step 3.
  5. If no credential exists, click New and create the appropriate credential type (Basic Auth or OAuth 2.0) with the exact alias name referenced by your spoke action.
⚠️

The credential alias must exactly match what's configured in the spoke action - case sensitive.

  1. If using OAuth 2.0, verify the token hasn't expired by checking the OAuth Entity Profiles related list on the credential record.
  2. For expired OAuth tokens, click Get OAuth Token to refresh, or configure Automatically refresh token checkbox to prevent future expirations.
  3. Navigate to MID Server > Servers and verify your MID Server status shows Up if the spoke requires external connectivity.
  4. Return to your spoke action configuration and verify each input field receives the correct data type - check that string data pills aren't mapped to integer/boolean inputs.
  5. If the spoke connects to an external API, navigate to System Web Services > Outbound > REST Message and locate the spoke's REST message.
  6. Click Test on the REST message to verify the endpoint URL is accessible and returns expected responses.
  7. Save all changes and test your flow by triggering it manually or through the trigger condition.
💡

Check Flow Execution Details under Process Automation > Flow Designer > Executions for detailed error messages if the action still fails.