Overview
This guide covers issues at the platform level — problems that affect access to UnifyApps itself or that cut across multiple automations at once. If you cannot log in, cannot load your workspace, are seeing API access errors across connections, or are experiencing connection failures that affect several automations simultaneously, start here.
Platform Troubleshooting overview
For issues specific to a single automation's run or step configuration, see the Automation Troubleshooting guide instead. For issues setting up a connection to a specific external service, see Connection Troubleshooting.
Note: Platform-level issues are sometimes caused by conditions outside your workspace — for example, a network policy blocking UnifyApps IP addresses, or an identity provider behaving unexpectedly during OAuth. Gathering as much detail as possible before contacting support will speed up diagnosis.
Common Platform Issues
Issue | Cause | Resolution |
|---|---|---|
Cannot log in — authentication fails or loops back to the login screen | Expired session, browser cache conflict, or an identity provider (OAuth/SSO) redirect mismatch. | Clear your browser's cookies and cache for the UnifyApps domain, then try again in a private/incognito window. If your organization uses SSO, confirm with your identity provider administrator that the redirect URL configured in your provider matches the URL expected by UnifyApps. If the issue persists, contact support@unifyapps.com with your organization name and the error message shown. |
OAuth sign-in redirects to an error page after authorizing | The redirect URL registered with the OAuth provider does not match the callback URL UnifyApps expects — a common misconfiguration when workspace URLs change or when multiple environments are in use. | Open your OAuth provider's application settings and verify the redirect/callback URL matches the UnifyApps URL for your workspace exactly, including protocol and any path segments. Double-check that credentials (client ID, client secret) are current and have not been rotated without updating the UnifyApps connection. Refer to Connection Troubleshooting — OAuth Redirection Issues for detailed steps. |
Workspace does not load or shows a blank screen after login | A browser extension, a stale cache, or a network proxy intercepting requests can prevent workspace assets from loading correctly. | Try loading the workspace in a different browser or in a private/incognito window with extensions disabled. If it loads there, disable browser extensions one at a time to find the conflict. If it does not load in any browser, check whether a corporate proxy or firewall is blocking requests to UnifyApps. Contact your network administrator to verify that UnifyApps domains and IP ranges are on the allowlist. |
API access errors across multiple connections at the same time | A shared credential (for example, a service-account API key used by many connections) has expired or been revoked, or UnifyApps IP addresses have been removed from an allowlist on the target service's side. | Identify whether the failing connections all share the same credential or target the same external service. If they share a credential, regenerate the API key or token in the external service and update the affected connections in UnifyApps. If they target the same service, verify that the service is available and that its allowlist still includes UnifyApps IP addresses. See Connection Troubleshooting — API Timeout Issues for IP whitelisting steps. |
Connection errors affect all automations that use a specific connection | The connection's stored credentials have expired, the external service's endpoint has changed, or SSL/TLS configuration is no longer valid. | Open the connection in UnifyApps and test it. Review the error details — look for HTTP status codes, timestamps, and the service's own error message. Verify that API keys or tokens are still valid by testing them directly in the external service's own console. Check that endpoint URLs and port numbers are still correct. If the service recently rotated its SSL certificate, ensure the certificate chain is complete and the TLS version is compatible. Refer to Connection Troubleshooting for a full checklist. |
Mandatory connection fields show as empty after saving | Required fields were not filled before saving, or a field value failed validation silently. | Reopen the connection and look for fields marked with an asterisk (*). Verify that every required field is populated and that the format matches what the service expects (for example, a URL with the correct protocol, or a token without extra whitespace). Save again and retest the connection. |
Automation runs stop appearing in Run History across all automations | Run logging has been disabled at the workspace or automation level, or a workspace-wide logging configuration change was made. | Open Run History for an affected automation. If you see Run logging is not enabled, click Enable Logging. If logging is on but no runs appear, confirm that automations are deployed and receiving trigger events. Check whether a Logging is off warning banner appears above the list, which indicates that logging was turned off after the last run was recorded. |
Cannot see or edit automations that should be accessible | Workspace role or permission settings restrict view or edit access for certain automations or folders. | Confirm with your workspace administrator that your account has the correct role and that the automation or folder is shared with you. A read-only automation shows the flow canvas and Preview tab but does not show the add-step controls or allow saving changes. |
Network or firewall blocks UnifyApps connections to external services | Corporate network policies or firewall rules prevent outbound connections from UnifyApps IP addresses to external endpoints. | Work with your network administrator to add UnifyApps IP addresses to the outbound allowlist for the affected ports. For services that require inbound connections from UnifyApps (for example, webhook-based triggers or database connectors), ensure that the relevant IP ranges are also on the service's inbound allowlist. If your organization requires encrypted tunnels, configure an SSH tunnel for the connection — see Connection Troubleshooting — SSH Tunnel Setup. |
Common platform issues table showing error types, causes, and resolution steps
Getting Support
If the steps above do not resolve your issue, contact the UnifyApps support team. To help diagnose platform-level problems quickly, include the following when you reach out:
A description of what you were doing when the issue occurred and what you expected to happen.
The exact error message or banner text shown on screen.
The browser and operating system you are using.
Whether the issue affects all users in your workspace or only your account.
Whether the issue affects all automations or only those using a specific connection or service.
Any recent changes to your workspace, connections, or network configuration that preceded the issue.
Reach the support team at support@unifyapps.com.
Notes
To make the most of Platform Troubleshooting:
Keep credentials for shared connections — especially service-account API keys used across many automations — documented and review them regularly so that expiry does not cause widespread failures.
Verify UnifyApps IP address allowlists whenever your organization's network policy changes, or when you set up a new external service integration.
Test a new connection immediately after setting it up, before relying on it in production automations, so that configuration errors are caught early.
Use a private/incognito browser window as a quick first check when you suspect browser state (cache, extensions, or cookies) is contributing to a login or workspace loading issue.
For issues that resemble OAuth redirect errors, always verify both the redirect URL in your identity provider and the credential values (client ID, client secret) — both must match what UnifyApps expects.
When a platform issue is resolved, re-enable run logging on any automations where it was turned off during diagnosis so that future runs are captured.