Implementing Random Delay in Orchestrated Processes to Prevent API Overload

Question

Hi everyone, 
 I'm working with an Orchestrated Process that calls an external API. Currently, all requests hit the endpoint simultaneously, causing it to return a 500 Internal Server Error due to overload. I'm seeing errors like this in the logs:

(2025-06-03 01:27:21.697) [810222] Error running script 'CCC_Custom_Universidade_ASAD'.
[System.Net.WebException] The remote server returned an error: (500) Internal Server Error.
 at StdioProcessor.StdioProcessor._Execute(Job job)
 at VI.JobService.JobComponents.ScriptComponent.Activate(String task)
 at VI.JobService.JobComponents.ScriptComponent._TaskScriptExec()
 at VI.DB.Scripting.ScriptRunner.Eval(String key, Object[] parameters)
 ---- Start of Inner Exception ----
 at DynScripts.Scripts_YJbLef26FdtP02l5bRVmtvwiRlf5MWGx.CCC_Custom_Universidade_DASA(String identificacao)
 at System.Net.WebClient.UploadData(Uri address, String method, Byte[] data)
 at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)

The script making the API call is CCC_Custom_Universidade_ASAD . I've included the full script below for reference. 
 My goal is to introduce a random delay within this process so that the API requests are staggered, preventing the endpoint from being overwhelmed. 
 Does anyone know if there's a built-in component or a recommended method in One Identity Manager (within an Orchestrated Process or a script like this) to achieve a random delay? I'm looking for a way to pause the execution for a random period (e.g., between 1 to 5 minutes) before each API call. 
 Any ideas or examples would be greatly appreciated! 
 Thanks in advance.

Barry Jackson · Accepted Answer

Hi Fernando, 
 Well you could use the DelayComponent - Delay ..... and generate the value for the delay - mins/secs I guess - in the pre-script of your process. But there's always going to be a chance that you'll hit the 500 error. I had a similar issue at my customer so in my process I call the API ..... if I go down the red path (error occurred) the next step checks the error ...... if it was a 400 simply end ..... if it was a 500 go to the next step ..... next step uses SQL to empty the ErrorMessages value from the API call step ..... then next step is DelayComponent - ReActivateJob .... so it loops back to the start. 
 This way the process will loop back until it stops getting a 500 error ...... to avoid an infinite loop the DelayComponent - ReActivateJob has a 'Retries' parameter. 
 Maybe this helps. 
 B.

Barry Jackson · Answer

Hi Fernando,

Sure .... so the process looks like this:

Ignore the 'Get the XDateInserted...' step .... that's something extra I needed for this target.

The step: 'CCC Check Error Returned'

Is: SQLComponent - Exists

WhereClause =

Dim f As ISqlFormatter = Session.SqlFormatter

Value = f.AndRelation ( _

f.Comparison("GenProcID", CStr(Variables("GenProcID")), ValType.String, CompareOperator.Equal, FormatterOptions.NonUnicodeLiterals), _

f.Comparison("JobChainName", myChain.Name, ValType.String, CompareOperator.Equal, FormatterOptions.UnicodeLiterals), _

f.Comparison("ErrorMessages", "%The remote server returned an error: (400) Bad Request%", ValType.String, CompareOperator.Like, FormatterOptions.UnicodeLiterals), _

f.Comparison("TaskName", "ExecuteCommand", ValType.String, CompareOperator.Equal, FormatterOptions.UnicodeLiterals) , _

f.Comparison("BasisObjectKey", $XObjectKey$, ValType.String, CompareOperator.Equal, FormatterOptions.NonUnicodeLiterals))

Then: 'CCC Clean up error messages of Provision XXXX Account'

Is: SQLComponent - Execute SQL

SQLStmt =

Dim Query As String = <![CDATA[

UPDATE JobQueue SET ErrorMessages=NULL

WHERE GenProcID = '{0}'

AND JobChainName = '{1}'

AND ErrorMessages <> ''

AND TaskName = 'ExecuteCommand'

AND BasisObjectKey = '{2}'

]]>.Value()

Value = String.Format(Query,CStr(Variables("GenProcID")),myChain.Name,$XObjectKey$)

HTH, Barry.

(And I hope the image of the process works as it's not showing up in this edit window!)

Implementing Random Delay in Orchestrated Processes to Prevent API Overload

Top Replies