Flow Data Stream Action parsing outputs.state = 'SKIP' stops pagination and further processing

Florian11
Kilo Sage

‎05-08-2024 05:58 AM

Hey, I've noticed something peculiar. When I use a data stream action with a script parser step, including the statement outputs.state = 'skip' for specific cases, there's a possibility that if all records on a pagination page (50 data records) are meant to be skipped, the entire action halts, and it doesn't proceed to the next pagination.
Is this intentional or a bug?

0 Helpfuls
  • 542 Views
1 REPLY 1

zbigniewbazydlo
Tera Contributor

‎08-22-2024 02:45 AM

Hi,

Indeed, we observe this behavior since years, I take it as a bug. We opened a HI CASE for this in Service Now and it was not solved so far. As a workaround we use our custom output variable isSkipped and we use conditional class therefore in ETL to check when we need to process those CIs further. This is not perfect as we anyway have to process records in ETL which could be skipped even before we create importset entry. This is not only scenario when Data Stream Action stops processing records farther, any exception that is thrown during load causes the the same even if it is related to only one page.   

0 Helpfuls