Warning: “Synchronize activities with Object Repository” – when and why is it required?

Help Studio Web
1

Hi everyone,

I’m working with modern UI activities and seeing a warning on my workflow:
“Synchronize activities with the Object Repository.”

I understand this is related to Object Repository, but I’m not fully clear on:
• Why exactly this synchronization is required
• What causes activities to go out of sync
• When should we use this option vs re-indicating elements manually
• Is it okay to avoid Object Repository and rely only on strict/fuzzy selectors?

2

Hi @Supriya_Borah,

If the Enforce Object Repository setting is set to Yes in Studio > Settings > Design > Design style , then you might get validation errors through out your workflow if the activities are not synchronized with Object Repository.

After below setting, it will disappear.

image
image688×683 57.8 KB

Please check the document for more details: Studio - Synchronize Object Repository tool

Yes, it’s okay to rely only on strict/fuzzy selectors, especially for smaller or simple automations.

However, the Object Repository is recommended for larger or scalable projects, as it helps with reusability, maintainability, and centralized selector management.

Thanks!

3

Hi @Supriya_Borah,

This warning is pretty common when using Object Repository.

Activities don’t store selectors directly when using Object Repository — they reference a shared UI descriptor. If that descriptor changes, activities can go out of sync. Sync just updates them.

  • Changes in Object Repository
  • UI changes in the app
  • Pulling updates from Git
  • Use Sync if the repository element is correct
  • Re-indicate if the element itself is broken or no longer matches UI

Yes, you can rely on selectors (strict/fuzzy), but Object Repository is better for larger projects.

Hope this helps :slightly_smiling_face:

Thanks,
Karthik

4

@Supriya_Borah This indicates that you have one or more activties in you code that have a proper selector but that selector has not been added to the object repository.Whereve you see the that message , you need to examine your workflow and correct all places where the activity is not using the repository