I’ve been analyzing he “Run Analysis” feature in Pega Robotic Automation v22.1 Robot Studio, I’ve reviewed the **documentation **and seeking further insight into the specific scenarios that would trigger certain warnings or errors. Understanding these situations will help us more effectively leverage the tool and proactively design robust automations. Could you please provide concrete examples or detailed explanations for the triggering scenarios of the following “Run Analysis” conditions, addressing our specific observations?
Project Analysis Categories:
Assets:
Invalid Exit Point: I’ve noted that Pega Robot Studio prevents adding multiple exit points in an Asset Automation. Are there other scenarios, beyond this design-time prevention, that could lead to an “Invalid Exit Point” error?
Invalid Member: I was unable to replicate this error. Could you provide a scenario where an “Invalid Member” error would occur?
Automation Content:
Invalid ASO Method: Pega Robot Studio prevents direct addition of ASO methods/properties in an Application method (Web adapter–>Interface). What specific scenarios would trigger this “Invalid ASO Method” error?
Deprecated Block and Control: What are the scenarios that would cause “Deprecated Block” and “Deprecated Control” errors?
Difference between Invalid Block and No Matching Member: Could you explain the precise distinction and triggering conditions between an “Invalid Block” error and a “No Matching Member” error ?
Robot Runtime Helper: What does the “Robot Runtime Helper” analysis check refer to, and under what specific conditions would it be triggered?
Runtime:
Duplicate ID: This check appears disabled. Are there any specific legacy scenarios, project migration issues, or other situations where the “Duplicate ID” check would still be relevant and active?
Context Keys:
Invalid Key : Smart: I was unable to replicate this check. Could you share specific scenarios that would trigger an “Invalid Key : Smart” error?
Missing Context Key: unable to replicate this check. What are the scenarios that would cause a “Missing Context Key” error?
A list of descriptions and conditions for each Project Analysis option under Assests, Automation Content, Runtime and Context key would be highly beneficial.
Your detailed insights into these points would be greatly appreciated and would significantly enhance our team’s ability to interpret and act upon “Run Analysis” results effectively.
Here’s the quick map of what Run Analysis flags in v22.1 actually mean, with concrete triggers. Invalid Exit Point fires if an Asset automation’s Exit shape is orphaned, duplicated by a bad merge, or wired from inside a conditional path that can never complete to the single defined exit (design-time blocks multiple exits, but you can still end up with an unreachable or dangling one after refactors). Invalid Member appears when an asset references a method/property that no longer exists after you renamed an adapter control or upgraded a package—think a stale signature in a block pointing at a removed member. Invalid ASO Method triggers when ASO-specific calls sneak into an Application/Adapter interface via pasted blocks or template reuse; fix by moving those calls into an automation and exposing parameters on the interface. Deprecated Block/Control shows up when your automation uses legacy palette items or UI controls that Pega has marked for replacement after upgrades—use the update/replace guidance to modern equivalents. Invalid Block vs No Matching Member: Invalid Block = the block is present but its signature or target type is wrong (parameter/type mismatch); No Matching Member = the target no longer exposes that method/property at all (renamed, removed, or different adapter). Robot Runtime Helper flags missing or mismatched Runtime-side helpers/config that the project expects (for example, required components not present or version drift between Studio and Runtime). Duplicate ID is mostly a migration/copy-paste artifact where two components share the same GUID; you’ll still see it on older projects brought forward. Invalid Key: Smart appears when an ASO/Context “Smart” key is malformed or not in the expected keyspace; Missing Context Key appears when a required key (set at design or via config) was never supplied at Runtime. For deeper knobs and release behaviors, see the 22.1 project analysis notes and Runtime component docs, and the general “deprecated controls” guidance for upgrade paths.
Invalid Exit Point: I’ve noted that Pega Robot Studio prevents adding multiple exit points in an Asset Automation. Are there other scenarios, beyond this design-time prevention, that could lead to an “Invalid Exit Point” error? - Not for this error.
Invalid Member: I was unable to replicate this error. Could you provide a scenario where an “Invalid Member” error would occur? - I am not sure how you would intentionally reproduce this. Essentially, if you had an automation inside an asset that referenced something outside of it. I suppose you could manually move an automation that used something global inside and asset to reproduce, but I have not tested that.
Automation Content:
Invalid ASO Method: Pega Robot Studio prevents direct addition of ASO methods/properties in an Application method (Web adapter–>Interface). What specific scenarios would trigger this “Invalid ASO Method” error? - I believe if you try to add ASO methods from the Toolbox, it would produce this error.
Deprecated Block and Control: What are the scenarios that would cause “Deprecated Block” and “Deprecated Control” errors? - I believe this is if you upgraded a project and were using something (perhaps like Robot Inspector) that was deprecated.
Difference between Invalid Block and No Matching Member: Could you explain the precise distinction and triggering conditions between an “Invalid Block” error and a “No Matching Member” error ? - I am not sure of the distinction here as this is not documented.
Robot Runtime Helper: What does the “Robot Runtime Helper” analysis check refer to, and under what specific conditions would it be triggered? - I am not aware of this as this is not documented.
Runtime:
Duplicate ID: This check appears disabled. Are there any specific legacy scenarios, project migration issues, or other situations where the “Duplicate ID” check would still be relevant and active? - I am not aware of this as this is not documented.
Context Keys:
Invalid Key : Smart: I was unable to replicate this check. Could you share specific scenarios that would trigger an “Invalid Key : Smart” error? - Usually this occurs when using keys and you have a chain of automation steps and somewhere down the chain one of the blocks has a key fitting defaulting to None. In my experience, it is caused by essentially having too many execution paths going to the same block.
Missing Context Key: unable to replicate this check. What are the scenarios that would cause a “Missing Context Key” error? - Similar to the above, if you have a key fitting set to None somewhere in your automation, it may require reconnection to properly calculate the upstream key.
@ThomasSasnett We wanted to set the best practice standards in our organization so we need these details to understand when and how these checks will be triggered which helps to guide the developers. Raised a SR INC-C46173 to check with Pega SME, routed back here as product team can only answer these queries.
Assets: According to Pega documentation and the project analysis feature in Studio, the screenshot displays the definitions for Assets.
****Invalid Exit Point: "Not for this error. "- How can we effectively replicate this check, and what are its triggering conditions? I’ve tried to trigger this check using the scenarios described, referencing Pega documentation and the project analysis option, that didn’t work. Refer the below scenarios:
“Application methods cannot have multiple exit points”- Unable to add more than one exit point in Application method Automation which is being handled during development by the studio.
“A public or private method in an assets can’t contain more than one exit point” - Unable to add more than one exit point in private/public utility method Automation.
Invalid Member: “I am not sure how you would intentionally reproduce this. Essentially, if you had an automation inside an asset that referenced something outside of it. I suppose you could manually move an automation that used something global inside and asset to reproduce, but I have not tested that.” Unable to understand, please provide the steps to reproduce this check.
Invalid ASO Method: **“**I believe if you try to add ASO methods from the Toolbox, it would produce this error.” - My understanding of ASO methods is conflicting. It is available in Utility automation and normal Automation. However, the project analysis option states that ‘ASO methods or properties invalid for use in an application method’. This contradicts my experience, as I’m unable to locate ASO methods within an application method Automation, despite the fact that Studio is already handling this scenario. Need your input in replicating.****
Deprecated Block and Control: “I believe this is if you upgraded a project and were using something (perhaps like Robot Inspector) that was deprecated.” I cannot replicate this scenario, but my query is clarified, I hope we haven’t observed this particular error till now.
Difference between Invalid Block and No Matching Member: " I am not sure of the distinction here as this is not documented." I have already reached out Pega SME, he routed me back here. Please help me in understanding.
Robot Runtime Helper: “I am not aware of this as this is not documented”-It has been confirmed by a Pega SME that it lacks formal documentation and readily available details. The SME plans to check and provide the Robot Runtime Helper documentation (INC-C46173)
Duplicate ID:" I am not aware of this as this is not documented."- I have already reached out Pega SME, he routed me back here. Please help me in understanding.
Context Keys:
Invalid Key : Smart: “Usually this occurs when using keys and you have a chain of automation steps and somewhere down the chain one of the blocks has a key fitting defaulting to None. In my experience, it is caused by essentially having too many execution paths going to the same block.” - Could please share a sample automation by replicating this error for my understanding?
Missing Context Key: “Similar to the above, if you have a key fitting set to None somewhere in your automation, it may require reconnection to properly calculate the upstream key.”- Could please share a sample automation by replicating this error for my understanding?
Could please share the list of descriptions and conditions for each Project Analysis option under Assests, Automation Content, Runtime and Context key (not only the highlighted ones in this question) would be highly beneficial?
