We've updated the ServiceNow Community Code of Conduct, adding guidelines around AI usage, professionalism, and content violations. Read more

Unable to run DataStream action in Flow Designer

MarkWe
Tera Guru

I'm trying to configure a Datastream action within flow designer.
However, when I test run the Datastream, I get an "Internal Server Error", and in the node logging I receive the following error message:

 

Invalid query detected, stack trace below [Unknown field element in table sys_flow_step_definition]

I have not used any scripts, the steps I went through were as follows:

  • Create the datastream
  • Under "Request" answer REST Step
  • Fill in the correct connection details and Request details on the Rest step
  • Press Test

(SoI have not added any inputs, outputs or scripts -- When I add them, this doesn't seem to change the outcome)

When I do the same in a "Normal" flow action with a REST step, this executes. But with the Datastream action I get the above error.

I'm hoping that I'm missing something terribly simple, but I can't figure out what.
Anyone else had the same issue and know a solution?

Working on a PDI on San Diego EA Patch 0 hotfix 1

find_real_file.png

find_real_file.png

find_real_file.png

1 ACCEPTED SOLUTION

MarkWe
Tera Guru

So, for future reference, I eventually was able to figure this out.

In the documentation, it states the following:

When designing a Data Stream action, you must create a single output of type Object or Dynamic Object. The Script Parser step maps items in the stream to this object using the targetObject global object.

The word must here is key. Since, apparently, if you don't have any output, this results in the internal server error.

I was working top-to-bottom on this, first trying to get the REST-call working, before worrying about output, but turns out, you have to 🙂

View solution in original post

5 REPLIES 5

Jake V
Tera Contributor

I can't believe this solution is still necessary in 2026! Talk about poor design. Most people work top-to-bottom and want to test the pagination before worrying about outputs. Either force an object output type on data streams or provide some signal to the developer that this is required before testing!!