Skip to main content
When something isn’t working as expected, the activity log is your best starting point. Every workflow run — including failures — is recorded there with full error details, timestamps, and payload data. Open Activity from the left sidebar before diving into the sections below.
Open the Activity log first. Most issues reveal themselves in the run history: you’ll see the exact step that failed, the error message returned, and the raw payload that was processed. This saves significant time before changing any configuration.

​
Workflow not running

Workflows only execute when they are set to Active. A workflow in Draft or Paused status will not respond to triggers or run on a schedule.
1

Open the workflow

Navigate to Workflows in the left sidebar and click on the workflow you want to inspect.
2

Check the status badge

Look at the status indicator at the top of the workflow editor. It will show Active, Draft, or Paused.
3

Activate the workflow

If the workflow is not Active, click the Activate button in the top-right corner. Confirm the prompt if shown.
Workflows return to Draft status if you save changes while they are active. You must re-activate after editing.
An incorrectly configured trigger is the most common reason a workflow does not run on time or doesn’t respond to an incoming event.
1

Open the trigger step

Click the trigger node (the first block) in your workflow to open its configuration panel.
2

For schedule triggers

Confirm the cron expression or schedule interval is correct. Check that the timezone is set to what you intended — a mismatch here causes runs to fire at unexpected times.
3

For webhook triggers

Copy the webhook URL shown in the trigger panel. Verify this exact URL is pasted into the sending service. Even a trailing slash difference will cause the request to miss.
4

Test the trigger

Use the Test trigger button to simulate an incoming event and confirm the workflow starts. For schedule triggers, use Run now to force an immediate execution.
If a connected integration has lost its authentication, workflows that depend on it will silently fail to start or stop mid-execution.
1

Go to the Integrations page

Navigate to Integrations in the left sidebar.
2

Look for error indicators

Any integration with a broken or expired connection will show a red warning badge. Click the integration to see the error detail.
3

Reconnect or re-authenticate

Click Reconnect and follow the OAuth flow, or paste a new API key if the integration uses key-based auth. Save your changes.
4

Re-run the workflow

After reconnecting, return to the workflow and click Run now to confirm it executes successfully.

​
Action failing

Every failed run includes a detailed error log that identifies exactly which action failed and why. Reading it carefully resolves most issues without further investigation.
1

Open the Activity log

Click Activity in the left sidebar to see all recent runs.
2

Find the failed run

Runs with errors are marked with a red Failed badge. Click the run to open the run detail view.
3

Expand the failed step

Each step in the run is listed in order. Click the step that shows a failure icon to expand it. You’ll see the full error message, HTTP status code (if applicable), and the data that was sent.
4

Act on the error message

Use the error text to identify the cause. Common messages and their fixes are covered in the accordions below.
If the error message mentions authentication failure, unauthorized access, or an invalid token, the credentials used by the action have expired or been revoked.
1

Identify the integration

Note which integration the failing action uses (for example, Slack, Google Sheets, or Salesforce).
2

Go to Integrations

Navigate to Integrations and locate that connection.
3

Reconnect

Click Reconnect to refresh the OAuth token, or click Edit to paste a new API key. Save your changes.
4

Retry the run

Return to the failed run in the Activity log and click Retry step to re-execute from the failed action without restarting the entire workflow.
Actions that send data to external services (creating a record, sending a message, posting to an API) often require specific fields. If upstream steps don’t produce the expected data, the action fails with a validation error.
1

Check the error detail

Open the failed step in the run log. The error message will typically list the field name that is missing or invalid.
2

Trace the data source

In the workflow editor, open the failing action and inspect the field mappings. Confirm each required field is mapped to a data source that is guaranteed to produce a value.
3

Add a condition or fallback

If the upstream data is sometimes empty, add a Condition step before the action to check for the value, and route to a fallback path when it’s missing.
Dynamic field mappings that reference optional trigger fields (like a form field that users can leave blank) are a common cause of intermittent failures. Use a default value or add a condition to guard against empty inputs.
When a workflow runs frequently or processes large batches, it may hit the rate limits of a connected service (such as sending too many emails per minute or making too many API requests per hour).
1

Identify the rate limit error

Look for HTTP 429 Too Many Requests responses in the run log, or error messages like “rate limit exceeded” or “quota exceeded.”
2

Add a delay step

Insert a Delay action between repeated calls to the same service. Even a 1–2 second delay can bring your request rate within the service’s limits.
3

Check the connected app's limits

Review the documentation for the connected service to understand their rate limit thresholds and reset windows.
4

Upgrade your plan if needed

Higher RCB Automation plans support priority execution queues that help manage high-throughput workflows. Contact support if rate limiting is a persistent issue.
You don’t need to restart an entire workflow from scratch when only one step fails. RCB Automation lets you retry from the point of failure.
1

Open the failed run

Go to Activity, find the failed run, and click to open it.
2

Locate the failed step

Scroll through the step list to find the step marked as failed.
3

Click Retry step

Click Retry step to re-execute that step using the same input data from the original run. The workflow continues from that point forward if the retry succeeds.
Retry step uses the original input data captured during the failed run. If the data itself was the problem, fix your trigger or upstream steps and run the workflow again from the beginning instead.

​
Integration connection issues

OAuth tokens for services like Google, Slack, and Microsoft expire periodically or are revoked when a password changes. Reconnecting takes less than a minute.
1

Navigate to Integrations

Click Integrations in the left sidebar.
2

Find the affected connection

Connections with expired tokens show a red badge or an “Authentication expired” warning. Click the connection.
3

Click Reconnect

Click the Reconnect button. You will be redirected to the connected service’s OAuth authorization page.
4

Authorize access

Sign in with the correct account and click Allow or Authorize. You’ll be redirected back to RCB Automation once the token is refreshed.
5

Verify the connection

The status badge should now show green. Any previously failing workflows will resume working on their next trigger.
If the connected service uses API key authentication and you’ve rotated the key, you need to update it in RCB Automation.
1

Copy the new API key

In the connected service, generate or copy the new API key. Keep this window open — you’ll need to paste it shortly.
2

Open the integration in RCB Automation

Go to Integrations, find the affected connection, and click Edit.
3

Paste the new key

Clear the existing key field and paste the new API key. Save the connection.
4

Test the connection

Click Test connection to confirm the new key is accepted by the service.
If the service supports multiple API keys simultaneously, generate the new key and update RCB Automation before revoking the old one. This prevents any downtime in your workflows during the rotation.
Some actions require specific permission scopes that may not have been granted when the connection was first authorized.
1

Read the error message

Open the failing run in the Activity log. Errors related to missing scopes typically say “insufficient permissions,” “access denied,” or reference a specific permission name.
2

Check required scopes

Review the integration’s documentation in RCB Automation (click the integration name to see its requirements) to find which scopes your action needs.
3

Re-authorize with expanded scopes

Go to Integrations, click the connection, and click Reconnect. During the OAuth flow, ensure the required permissions are checked. Some services require you to log in as an admin to grant certain scopes.
4

Check the connected app's settings

For API key integrations, go directly to the connected service and verify the API key has the necessary permissions or roles assigned.

​
Webhook not receiving data

A single character difference in the webhook URL means the sending service is posting to a different endpoint entirely.
1

Open the trigger configuration

Click the webhook trigger node in your workflow editor to open its configuration panel.
2

Copy the URL

Click the Copy button next to the webhook URL to copy it to your clipboard. Do not manually type or re-type the URL.
3

Paste into the sending service

Go to the sending service’s webhook settings and paste the URL directly. Replace any existing URL entirely — do not append or edit the existing one.
4

Send a test event

Use the sending service’s “Send test” or “Test webhook” feature. Then check the Activity log in RCB Automation to confirm the event was received.
RCB Automation webhook triggers only accept HTTP POST requests. A GET request to your webhook URL will be ignored.
1

Check the sending service's method setting

In the sending service’s webhook configuration, look for an HTTP method setting. It must be set to POST.
2

Check the Content-Type header

Most integrations expect a Content-Type: application/json header. If the sending service sends application/x-www-form-urlencoded or multipart/form-data, the payload may not parse correctly.
3

Check the Activity log for received requests

Even malformed or incorrectly-typed requests will sometimes appear in the Activity log. Look for entries with unexpected status codes or empty payloads.
If the sending service only supports GET requests, you cannot use it as a webhook source. Consider using RCB Automation’s polling trigger (schedule + HTTP action) to fetch data from that service on a defined interval instead.
When a webhook fires but your workflow doesn’t behave as expected, inspecting the raw payload reveals what data was actually received versus what you expected.
1

Open the Activity log

Navigate to Activity and find the run triggered by the webhook event.
2

Click the trigger step

In the run detail view, click the trigger step to expand it. You’ll see the full raw payload exactly as it was received.
3

Compare with your field mappings

Check that the field names in the payload match the field references you’ve used in downstream steps. Field names are case-sensitive — userId and userid are different.
4

Adjust your workflow mappings

If the payload structure differs from what your workflow expects, update the field references in your action steps to match the actual payload structure.

​
Performance and delays

RCB Automation executes workflows through a queue system. Under normal conditions, workflows start within a few seconds of being triggered. During periods of high platform load, there may be brief delays before your workflow begins.
1

Check the run timestamps

In the Activity log, compare the Triggered at time with the Started at time. A gap of more than 30 seconds during off-peak hours suggests a queue delay.
2

Check platform status

Visit the RCB Automation status page to see if there are any active incidents or elevated queue times affecting all customers.
3

Review workflow complexity

Workflows with many steps, large data transformations, or loops over large datasets take longer to complete. Break very large workflows into smaller sub-workflows where possible.
Scheduled workflows (cron triggers) are placed in the queue at their scheduled time. If the queue is busy, a scheduled workflow may start slightly after its scheduled time. This is expected behavior and does not indicate an error.
If your workflows consistently experience delays or you need to process high volumes of runs concurrently, upgrading your plan provides access to priority execution queues and higher concurrency limits.
1

Review your current usage

Go to Settings > Usage to see your current run volume, average queue time, and how close you are to your plan’s limits.
2

Compare available plans

Click Upgrade plan to see a comparison of throughput limits, concurrency settings, and execution priority across plans.
3

Contact support for enterprise needs

If you need custom throughput guarantees or dedicated execution infrastructure, contact support@rcbautomation.com to discuss enterprise options.