The issue:
DSS iD - 9032730
Hello @neha.kabra,
It could be that the time at which DSS processed the instruments or when your application uploads it to sftp have changed. From DSS standpoint there should be no difference between manually uploading a file, vs programmatic upload of the same file.
Either way, I would recommend that you raise this issue with DSS product team, who can take a look at sftp logs and advise why this is happening.
Hi @Gurpreet
Thanks for your response.
Schedules run at 2:30 AM and 7 AM london time.
The Import process starts at 06:40 from 7 AM extraction. Appreciate your assistance, do let me know if we can discuss this directly with the client.
NOTES
Import process started... (04/18/2024 06:40) (diagnostic: 20240418 05:40:12.AM UTC)User ID: 9032730Request Correlation ID: CiD/9032730/AAAAAA.08e1b051c9a9c0ac/FW.187181607Instrument List Import Results: Successfully imported 749 instruments in 00:00:10.Standard Segment Counts (717 Total)Equity 716Mutual Fund 1Historical InstrumentsHistorical 2Instruments not found or restricted content (30):ISN, ES0148396007 (not found)ISN, ES0130670112 (not found)ISN, CH0012221716 (not found)ISN, CH0102484968 (not found)ISN, CH0038863350 (not found)ISN, CH0012005267 (not found)ISN, CH0012032048 (not found)ISN, CH0126881561 (not found)ISN, ES0144580Y14 (not found)ISN, ES0113211835 (not found)ISN, CH0016440353 (not found)ISN, CH0024608827 (not found)ISN, CH0013841017 (not found)ISN, CH0012549785 (not found)ISN, CH0418792922 (not found)ISN, ES0113900J37 (not found)ISN, CH0025751329 (not found)ISN, CH1175448666 (not found)ISN, CH0210483332 (not found)ISN, CH0024638196 (not found)ISN, CH1256740924 (not found)ISN, CH0244767585 (not found)ISN, CH0011075394 (not found)ISN, CH1326854028 (not found)ISN, ZZ0M28434583 (not found)ISN, ES0173516115 (not found)ISN, CH0130293662 (not found)ISN, CH0012142631 (not found)ISN, ES0109067019 (not found)ISN, CH0010570767 (not found)****** MACHINE READABLE NOTES ******ITEM TYPE: INSTRUMENT LISTNAME:MIFL to Refinitiv Instrument ListACTION:REPLACELINE#: 42LINE STATUS: NOT FOUNDLINE#: 45LINE STATUS: NOT FOUNDLINE#: 193LINE STATUS: NOT FOUNDLINE#: 194LINE STATUS: NOT FOUNDLINE#: 195LINE STATUS: NOT FOUNDLINE#: 196LINE STATUS: NOT FOUNDLINE#: 198LINE STATUS: NOT FOUNDLINE#: 199LINE STATUS: NOT FOUNDLINE#: 240LINE STATUS: NOT FOUNDLINE#: 276LINE STATUS: NOT FOUNDLINE#: 319LINE STATUS: NOT FOUNDLINE#: 386LINE STATUS: NOT FOUNDLINE#: 387LINE STATUS: NOT FOUNDLINE#: 389LINE STATUS: NOT FOUNDLINE#: 390LINE STATUS: NOT FOUNDLINE#: 398LINE STATUS: NOT FOUNDLINE#: 424LINE STATUS: NOT FOUNDLINE#: 426LINE STATUS: NOT FOUNDLINE#: 427LINE STATUS: NOT FOUNDLINE#: 428LINE STATUS: NOT FOUNDLINE#: 429LINE STATUS: NOT FOUNDLINE#: 430LINE STATUS: NOT FOUNDLINE#: 431LINE STATUS: NOT FOUNDLINE#: 443LINE STATUS: NOT FOUNDLINE#: 450LINE STATUS: NOT FOUNDLINE#: 537LINE STATUS: NOT FOUNDLINE#: 565LINE STATUS: NOT FOUNDLINE#: 646LINE STATUS: NOT FOUNDLINE#: 696LINE STATUS: NOT FOUNDLINE#: 707LINE STATUS: NOT FOUND****** END MACHINE READABLE NOTES ******Import process completed (04/18/2024 06:40) (diagnostic: 20240418 05:40:24.AM UTC)
Please raise this issue with DSS product team. We don't have any visibility into the operational aspects of the services and won't be able to tell why the import is failing.