We just imported our flow from test box to our production box and started our ru

Check the Scheduling tab for that node and the Other Tab for misconfigurations.

yes i checked that and there is nothing in that node.

Looking at your Model with Shireesh I noticed that you have a timer configured with the following recurrence

=rule!getIntConstBasedOnEnv("MINOR_RA_JIRA_CDT_REFRESH_DELAY")

but the environment is missing the MINOR_RA_JIRA_CDT_REFRESH_DELAY constant

Since you are using a custom function to find constants by name they won't be detected by the Missing Dependencies Checker so you need to be careful with including all the required constants. Simply export this one and bring it to this environment.

Don't re-create the constant, you better export and import so it preserves its UUID in case you are referring it in other place and not only in your custom function.

yes after bringing these constants its able to proceed further. appian should give better error message as to what its erroring on and also produce the dependency check accurately.

It's very important to remember that the dependency checker, and pretty much everything in Appian, works based on the UUID of the objects; a text in quotes, even if it's the name of a constant, is considered a string which can represent anything in the system that's why when building custom functions that work with constant names you need to be careful and keep in mind this design so you don't miss including them in the package.

On the other hand it is always better to analyze the server.log for a more detailed error since the alerts will usually just contain a summary of it.

even the server.log is not giving the name of the constant that is missing, its so encryptic

your custom function getIntConstBasedOnEnv() is a better place to catch the exception properly (in the log file, since you don't want to throw an exception from custom function) ?

how do I tell it to catch exception if the function itself is not there?