Inconsistent response times on Forge Storage API (get and set)


A customer reported that my app is timing out randomly - which was not the case before.

I’ve set up call logging and found out that a single storage.get or storage.set call may take anywhere between 0.3 to 6 seconds to complete, with the exact same amount of data returned or stored.

Have anyone else noticed the same inconsistency? From the Atlassian side, is there an SLA or SLO for Storage API response times in place or plans to implement and follow one?


1 Like

Hey @IgorAndriushchenkp
We don’t have any public SLO at the moment but I’ll talk to the team about it. In the meantime could you tell me how you are measuring the performance?

I’ll follow up on this internally and get back to you :slight_smile: