By default, scheduled Import job runs after 12 hrs. interval in production environment. If blueprint's last modified time is greater than schedule import job's last run time then only job will update catalog item. Scheduled import run interval is configurable property and can be changed as per requirement.
Manual execution will not work unless property 'CatalogImportLastRunTime' value is cleared from the system. For forceful execution, please clear value of 'CatalogImportLastRunTime' and re-run the scheduled import job.
I suggest delete only modified catalog item or blueprint from Catalog, clear value of 'CatalogImportLastRunTime' property (highlighted in yellow) from Integration-vRealize Automation and re-run the scheduled import 'vRealize-Automation-ImportCatalogItems'.
Thank you for the suggestion. This allowed me to properly run a forced execution of the scheduled imports. After doing so, it appears to properly pull in the changes made to the catalog item. I'm a bit frustrated that manual intervention has been required. One would assume that the scheduled runs would find changes and update the SNOW resources.
I also noticed this issue with updating CMDB entries from the vRA machine details. Following your steps above allowed the CIs to obtain the correct data. Again, not thrilled that I had to perform this process to pull information that is supposed to be gathered by the scheduled imports.
This process auto pull all changes but only on production service now instances. Scheduled Import job will not auto run on dev instaces. Hence we need to follow manual steps.
Gotcha. I appreciate the prompt response!