Webservice Pooling: Automate API Retries Without the Headache

Features to Discover
1

Webservice Pooling: Automate API Retries Without the Headache

When an application calls an external service (HRIS, ERP, DMS, etc.), that service may not always respond immediately.

Instead of showing an error or blocking the user, ROK offers a smarter solution: automatic pooling.

:bullseye: What Is Pooling?

Pooling allows ROK to automatically re-query a webservice until it gets a response:

  • at a defined interval (every 30 seconds, 2 minutes, etc.)
  • for a maximum duration (e.g., 10 minutes)
  • without any manual intervention

automatically re-query a webservice
automatically re-query a webservice675Ă—938 92.7 KB

:briefcase: Real-World Examples

:small_blue_diamond: You launch a process to create a user account in an HRIS. The external API may take a few seconds to respond.
With pooling, ROK keeps checking in the background until confirmation is received.
The user does nothing. No failure. No blocked task.

:small_blue_diamond: A PDF generation service is temporarily overloaded.
ROK keeps retrying until the file is generated and returned.

:gear: How Is It Configured?

In the process designer, simply enable the “Pooling” option on a server task or API call.

You can define:

  • the number of retry attempts
  • the interval between each attempt
  • the fallback behavior if the service still fails (e.g., alert, alternate path…)

Pooling” option on a server
Pooling” option on a server685×619 60.8 KB

:white_check_mark: Why It’s Smart

  • Improves the resilience of your connected applications
  • Prevents process interruptions due to temporary service issues
  • Reduces the need for manual support or error handling