The “Object not set to an instance of an object” error when reading an Excel workbook often means the file or the worksheet cannot be found or accessed.
Since the error happens inside the loop on the second Read Range, perhaps this is the problem.
The most common causes are related to timing and file access:
File Lock: Your creationofsheet.xaml likely opens the Excel file (filepath). Maybe the problem is that the invoked workflow is not closing the file quickly or correctly, leaving it locked when the second Read Range tries to access it.
Sheet Existence: While sheetName has a value, perhaps the sheet does not exist in the workbook at that exact moment. The name might be slightly different, or the invoked workflow failed to create it properly.
You could try adding a small delay (1-2 seconds) before the second Read Range Workbook activity. This gives the file time to close and release the lock.