Home General Discussion

Service Request Status Update

Kiran_AlaKiran_Ala Customer IT Monkey ✭


We have few Request offerings which runs the Runbook Workflows to do some activities. The backend runbook workflow is finishing in less than a minute but it is taking around 5 minutes to update the status in the Cireson Portal.

Does anyone faced this situation? Are there any settings that we could change to update the status more often?



  • Konstantin_Slavin-BoKonstantin_Slavin-Bo Customer Ninja IT Monkey ✭✭✭✭
    edited June 2017
    The bottleneck is SCSM itself and not the Cireson Portal. SCSM takes a while to communicate with Ochestrator, both to start a RB activity and to register it has completed. Unfortunately, I don't think there's any way to optimize the communication between the servers, apart from making sure, that the servers has the needed resources, and the network between them is fast enough.
Sign In or Register to comment.