Skip to main content

Refresh

Refreshes the current page in the browser.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Input​

  • Page Id - Id of the page to refresh. This ID is generated by the Open Browser node.

How It Works​

  1. The node receives the Page ID
  2. It validates that the Page ID is not empty
  3. It waits for any configured delay before execution
  4. It retrieves the active page session using the provided Page ID
  5. The node sends a refresh command to the browser
  6. The browser reloads the current page from the server
  7. All page content, JavaScript, and resources are reloaded
  8. The node applies any configured delay after execution

Requirements​

  • An active browser session created by the Open Browser node
  • A valid Page ID from the Open Browser node
  • The browser page must be active and not closed

Error Handling​

Error CodeDescription
Core.CSV.AppendCSV.ErrOnCreateConfiguration parsing error during node creation
Core.CSV.AppenCSV.OnMessageError parsing incoming message data
Core.Browser.Refresh.ErrPageIdPage ID is empty or not provided
Core.Browser.Refresh.ErrSessionInvalid or expired Page ID, session not found
Core.Browser.Refresh.ErrFailedFailed to refresh the page

Usage Examples​

Example 1: Refreshing After Data Update​

When data on a page changes and needs to be reloaded:

1. Use Open Browser and navigate to a dashboard page
2. Perform actions that trigger data updates on the server
3. Use Refresh to reload the page and display updated data
4. Use Wait Element to ensure page is fully loaded
5. Continue extracting updated information

Example 2: Handling Stale Page State​

When page becomes unresponsive or stale:

1. Detect stale state (timeout on element interactions)
2. Use Refresh to reload the page
3. Wait for page to fully load (add Delay After or use Wait Element)
4. Retry the failed operation
5. Continue automation with fresh page state

Example 3: Periodic Data Collection​

When monitoring a page that updates periodically:

1. Navigate to a monitoring or status page
2. Extract current data using Get Value nodes
3. Store the data
4. Use Refresh to reload the page
5. Wait for configured interval
6. Repeat the extraction process in a loop

Usage Notes​

  • Refresh reloads the entire page from the server (not from cache)
  • All dynamic content and JavaScript state is reset
  • Form data entered by the user may be lost unless saved by the browser
  • Session cookies and authentication are typically preserved
  • Some pages may show confirmation dialogs before refresh
  • Page load times affect how long the refresh takes
  • Network conditions impact refresh speed
  • Add appropriate delays after refresh to allow page to fully load

Tips​

  • Always add a delay after refresh to allow the page to load completely
  • Use Wait Element after refresh to confirm critical elements are loaded
  • For pages with heavy JavaScript, increase Delay After appropriately
  • Consider using Continue On Error for pages that occasionally fail to refresh
  • Monitor network conditions if refresh operations are timing out
  • For pages with auto-refresh, check if manual refresh is needed
  • Test refresh behavior as some SPAs may not respond well to full page refresh
  • Combine with Try-Catch to handle refresh failures gracefully