Ok, got it, thank you.
Another question here:
I have a coded workflow library used in a web project. Let’s say is version 1.0.1.
I update the library and publish again to Orchestrator Tenant Library Feed to version 1.0.2.
I open the web project using Studio Desktop, update the reference to the version 1.0.2 of the library.
I’m syncing again in web. The web project should contain now a reference to the updated library, right?
Most of the times, I have an error here
This might be the case. Does this happen every time you do it this way, or only occasionally?
Edit. I think there is a delay of up to 1 hour for the service behind the activities search engine to start showing the new activities. Let me test something and I’ll come back with more information
I verified my assumptions and chatted with the team for further insights.
The short answer is that the search service, which links what is published on the feed with what shows up in Studio Web, is refreshed on a schedule. This means there might be up to an hour delay before your custom activity appears in SW.
This also means that your attempts to republish weren’t effective, and simply waiting would have been enough.
I tested this with a solution in Studio Web that contained a custom library version 1.0.1. I then published another version (1.0.2) and tried the following:
immediately refresh it → it remained at 1.0.1
refresh it after 1 hour → it auto-updated to 1.0.2
Once the search service refreshes, you will see your activity in Studio Web. There is no need for any Studio Desktop adaptations if you simply want to add the new library activity to the project in Studio Web. Anything published to the orchestrator feed should appear in Studio Web (albeit with that maximum 1-hour delay):
