-
Type:
Task
-
Resolution: Unresolved
-
Priority:
L3 - Default
-
None
-
Affects Version/s: None
-
Component/s: backend
-
2
-
S
When a user creates a cluster in the cloud, it can be that their first action is to create and deploy a process. By the time this is deployed, Optimize's import pipelines might have backed off up to 30 seconds (or their configurable amount), meaning that there is a somewhat unnecessary delay in the import of that first process. It would be a cleaner experience for users to be able to see that first process almost immediately.
We should investigate whether or not it makes sense to delay back off for the first x number of minutes of operation after Optimize starts up
ATs:
- Importers can be configured to delay the starting of backing off
- Documentation is updated
- For SaaS customers, a sensible default is used
Justification:
Users expect data to be instantly available in Optimize in the case where there is not a backlog of data to be imported. The backoff behaviour is unclear and this will make the user's first cloud experience a bit smoother