Troubleshooting: Network Connectivity and Tenant Performance

Verify that you configured proxies to trust the IP range and domain names of Workday. Refer to the Workday Data Centers page for information about your tenant location, DNS names, and IP addresses.
Verify that you aren't accessing Workday tenants or Workday servers on HTTP port 80. Workday servers use port 80 only for redirecting to HTTPS port 443.

Determine if the cause of the performance lag is with your corporate network or with the Workday tenant. Sign in to the Workday tenant from outside your corporate network. If necessary, modify your authentication policies so that you can connect to Workday from outside the corporate network temporarily. We recommend that you access Workday only from secured and trusted connections and not from public access points.

If the problem continues, continue your investigation with your Workday tenants.

If the problem no longer occurs, focus your investigation on your corporate network settings:

Remove restrictions on the number of sessions that can access your network.
Increase the timeout settings for predefined session timeouts. Ensure they’re long enough to enable all Workday reports to run to completion.
Don't filter, modify, or otherwise alter content from the Workday tenant to your network.
Don't override cache control headers of content from the Workday tenant to your network.

Access the

System Health Dashboard

(secured to the

System Monitor Administrator

security domain) to identify possible resource bottlenecks and adjust future schedules. When running a batch process, consider splitting it into smaller chunks or running it during off-peak hours. Example: The Data Scrambler process can take 10 hours or longer, and it isn’t critical to your current project. Consider scheduling it over the weekend or during nonwork hours.

Access the

Process Monitor

(secured to the

My Reports

security domain). View details about specific processes and cancel the processes that are contributing to performance lag. Example: A custom integration that depends on a third-party service is using a lot of resources during work hours. To determine its performance, view the Consolidated Reports section for the process in the

Process Monitor

. Cancel the process, if needed.

Verify that you have TCP keep-alive enabled. If enabling TCP keepalive isn't possible, increase the timeout settings for the predefined session timeouts of your proxy or firewall. Ensure they're long enough to enable all Workday reports to run to completion.