You are viewing limited content. For full access, please sign in.

Discussion

Discussion

Cloud BP - Retrying a rule does not properly retry the rule - Can I put a try catch repeat interrupt anything?

posted on February 15, 2024

Every time I use the Retry option from the Monitor page it throws the same error that an object reference is not set to an instance of an object. However testing the rule works perfectly fine.

So I know if it truly was retrying the rule, it would work and as a workaround I just copied the rule in the BP diagram and published to all instances like this:

Then I skipped the rule instead, so it would truly retry the rule and now it succeeded.

I have had a case open for over a week now to get the object reference errors fixed and meanwhile dozens of processes are getting stuck so I want a way to have this done automatically anytime a rule will not run.

There is no timer event available on rules and no try catch though. How do I get the process to retry if it runs into an error so that things don't just sit there?

People are not getting notified, submissions are not getting seen by the departments that need to know about them. It is a major hold up in the BP and the rule is necessary to continue the process as it looks up who is responsible for the submission.

0 0
replied on February 16, 2024

As indicated in the support case, the error is caused by attempting to run the rule and timing out. The process has retried, reached its automatic attempts limit and suspended. You are correct that the error message is not what a user should see and we'll fix that.

Please attach the requested error logs to your support case so we can investigate why the rule failed repeatedly.

0 0
replied on February 16, 2024

These must be retries not shown. On each instance I only see the initial failure and when I click retry it continues to say object reference not set to an instance of an object. This is why I need an interrupt path that leads back to itself, so that it actually retries after an hour or a day or so.

0 0
replied on February 16, 2024

Correct, the task does a series of quick retries for a few minutes before suspending. When you retry it, it does the same thing again.

It's unlikely that an hour or a day later would work, if your manual retry didn't get it working. But we can't tell for sure without the remote agent logs requested in the support case.

0 0
replied on February 16, 2024

When I manually re-run the rule as shown above, or from a test, it does work, a day / hour / month later. The retry button on the monitor page is not working properly and this is why I have to duplicate the rule.

Trying to get the logs, but I don't see why the problem would be there when the rule is working just fine.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.