Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check Target exists before executing activity #102

Closed
FIMTooler opened this issue Apr 15, 2021 · 2 comments
Closed

Check Target exists before executing activity #102

FIMTooler opened this issue Apr 15, 2021 · 2 comments

Comments

@FIMTooler
Copy link

Have a couple of MPRs that trigger on Transition Out as well as when any attribute on an object is modified (last modified timestamp situation). Thus when an object gets deleted, MPRs performing further changes are triggered. Of course since the Target is deleted, they fail with PostProcessingError.

I did finally find that it's mentioned on the Delete Wiki that only [//Target] is remaining after a deletion. Since the deletion activity itself was functioning correctly, it wasn't intuitive to look at that wiki to find that out.

Referencing any attribute on the Target results in the workflow crashing and the stack trace in the request saying "Permission Denied" "ResourceIsMissing". Even if the Query or Activity Execution Condition field reference an attribute other than [//Target] failure will occur immediately as the failure seems to happen at the lookup level when it tries resolving.

I came up with this solution to prevent the Update activities (or any other WAL activity) from executing if the Target no longer exists. It might be useful to stuff this into the wiki somewhere for others to easily find.

image

@NileshGhodekar
Copy link
Contributor

Hi @FIMTooler, thx! Let me see what is the best place to link this.

@NileshGhodekar
Copy link
Contributor

I've linked this up in the wiki's for Activity Execution Condition, Query Resources and also Update Resources Activity. Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants