The user has two variables which are missing on their SCTASK record even though they have specified that they should be carried over in their Catalog Task workflow activity via the slush bucket.
A custom Catalog UI Policy is the culprit, and why the user is seeing the behavior.
As mentioned above, the custom Catalog UI Policy is causing the issue.
The user can easily test this by navigating to the policy and setting it to active = false.
Then, when they reload the affected SCTASK record, both of the previously hidden variables display properly, per the user's expectation.