Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Flow fails on setting MinimumAgeForProcessing property in ms



The flow fails on setting the MinimumAgeForProcessing property in milliseconds (ms) in the Queue-For-Agent method.

Error Messages

Not Applicable.

Steps to Reproduce

  1. Log in to the application
  2. Get the DateTime difference for a date >25 days in MinimumAgeForProcessing property in milliseconds which comes up to 2160000000
  3. Set it in the Queue-For-Agent method on a post activity of local action and save it to an activity

Root Cause

A defect or configuration issue in the operating environment. The MinimumAgeforProcessing property is mapped to an integer and does not support a value more than 2147483647 in milliseconds.


Perform the following local-change:

Use the enqueue() method instead of using the Queue-For-Agent method to use pyMinimumDateTimeForProcessing for scheduling an agent as per a given date in future.
  1. Perform a Page-New  > StepPage1
  2. Use Property-Set:

    StepPage1.pyAgentName    to   [Agentruleset:AgentName]  e.g. "Pega-ProCom:ServiceLevelEvents"
        StepPage1.pyItemStatus      to   "Scheduled"
        StepPage1.pyMaxAttempts  to    Value
        StepPage1.pyMinimumDateTimeForProcessing   to  @DateTime.addToDate("20180418T013020.420 GMT","5","10","10","10")     [Use datetime library here to compute curent date + 25 days]

  3. Add the below JavaScript:
     try {
         catch (DatabaseException de)

  4. Commit the rule

Published August 24, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us