How to handle big tasks in scrum without increasing the sprint?

Question

Agile

Sprints are 2 weeks long and in general they meet the needs of the business, but from time to time there are tasks when it is impossible to implement a refinement that carries business value in one sprint.

For example, there is a big task that starts with the background process "Loading and processing data from an external system" - it takes about 2 weeks to do this and does not bring business benefits. How to implement such tasks according to best practice in scrum?

• Optionally expand the sprint?
  
• Accept the risks that the result of the sprint does not benefit the business?
  
• Something else ?
  

Answer 1

Break stories into smaller tasks and complete them within a sprint. And sprints never correlated with business value.