Summary
Based on what I saw in your org, there are two ways to solve the issue: either you add Page Assignments for the second custom object, or you add the Skuid page name to your Visualforce Markup.
Background information
As far as I can see, you use Page Assignments for the first object. The Page Assignment settings can be found in Skuid if you click “deploy” in the top menu bar. You need those Page Assignments because you used the Visualforce Markup without the Skuid page name. That is possible, please see this documentation:
https://docs.skuid.com/latest/en/skuid/deploy/salesforce/visualforce/skuid-page-visualforce-component.html#basic-overrides-with-page-assignments
Unfortunately, there are no Page Assignments for the second object, that’s why it doesn’t work. You can now either add Page Assignments like it has been done for the first object. Or, you can change the Visualforce Markup and include the Skuid Page name, then you wouldn’t need Page Assignments. Please see this documentation:
https://docs.skuid.com/latest/en/skuid/deploy/salesforce/visualforce/skuid-page-visualforce-component.html#basic-overrides-without-page-assignments
