Force async processing for large data sources on restricted domains #35465
+27
−10
Task list completed / task-list-completed
succeeded
Dec 13, 2024 in 0s
3 / 3 tasks completed
All tasks have been completed
Details
Required Tasks
| Task | Status |
|---|---|
| This PR can be reverted after deploy with no further considerations | Completed |
| Risk label is set correctly | Completed |
| The set of people pinged as reviewers is appropriate for the level of risk of the change | Completed |
| I was hesitant to process the data source asynchronously if it was not marked to do so | Incomplete |
| I was hesitant to set something on the data source, which was created by the user & that too without the user knowing about it. We could else then mark it as async but also notify user we did so, along with explanation, which seemed to get too stretched for the implementation. So, I chose to rather tell the user to do so, which has an additional benefit of user getting aware of this feature and using it more actively in future. | Incomplete |
Loading