Question
RBC
CA
Last activity: 21 Oct 2025 12:57 EDT
Block has invalid upstream key
We have a call to interaction manager's GetTable function to retrieve the count of backlogged tasks in it's queue, the function has a Key parameter that is set to None, and the function works well in the Robot Studio, and legacy Visual studio plugin. When we attempt a deploy from the Robot Studio UI, an error is trapped indicating "Automation block has an invalid upstream key - KeyName: None". (see attach pic)
A work around was noted in the support logs (https://support.pega.com/question/automation-block-has-invalid-upstream…) on how to change the Robot Studio to ignore the error. However, is this an error, or not? Is there a better way to get the count of items on the queue?
Our challenge is that we have to tell each developer that this is not an "error" and the default option of the "Project analysis" needs to be altered.. I would like a clean compile every time, Especially on the attached sample, as it is used by all our solutions at somepoint...
Accepted Solution
Updated: 21 Oct 2025 12:57 EDT
Pegasystems Inc.
US
@RobIsTheName This is great feedback. I will pass this along to the product team.
Pegasystems Inc.
US
@RobIsTheName I can't really think of a better way here as this specific usage of the Interaction Framework is valid. In this case, there is only a single table and a key of none will work.
The best way to handle this would be to mark that category as a warning instead of an error. You can distribute your PegaStudioConfig.json once configured to all your developers so that they share the same Project Analysis settings.
RBC
CA
@ThomasSasnett Thanks for the quick reply.
The only concern I have with the recommendation, is people questioning why it was flagged in the first place as an error. Several times, folks have questioned the code on deployments, thinking there is something wrong, and then spending time trying to find a solution, when there isn't one needed.
Shouldn't Pega pencil in a fix for the Project Analysis to not flag this instruction as "Error".
Accepted Solution
Updated: 21 Oct 2025 12:57 EDT
Pegasystems Inc.
US
@RobIsTheName This is great feedback. I will pass this along to the product team.