topic Re: File Input message 0 records were read from file (limit reached) in Alteryx Designer Desktop Discussions

File Input message 0 records were read from file (limit reached)

MJ — Tue, 18 Jun 2019 14:27:48 GMT

I just saw a File Input message type for the first time today and this is the only community article I could find that seemed relevant.

It appears on the validation run messaging after we tried to publish to the Gallery.

Alteryx Workflow Input Files to be uploaded...0 records were read from "<filename>" (limit reached)

Does this mean that the server capacity has reached it's limit?

I couldn't find anything to confirm this, so I thought I'd add a softball question for it :)

Thanks,

Re: File Input message 0 records were read from file (limit reached)

JoeS — Tue, 18 Jun 2019 14:38:38 GMT

Hi @MJ

Just wanting to check if you have an output in your process?

This message can come when there is no output and the server looks to be efficient and realise this, thus not running the process if there is no output.

Re: File Input message 0 records were read from file (limit reached)

MJ — Tue, 18 Jun 2019 15:05:42 GMT

It only has the Publish to Tableau Server macro at the end.

Would adding a file output workaround this?

Re: File Input message 0 records were read from file (limit reached)

JoeS — Wed, 19 Jun 2019 09:36:12 GMT

Ah, it's not quite what I thought then.

Are you able to upload the full message log of when you run the workflow on the server?

Re: File Input message 0 records were read from file (limit reached)

MJ — Wed, 19 Jun 2019 15:31:34 GMT

I can do screenshots and think I learned it's a non-issue this morning...

Validation Run shows the "limit reached" at the end of the message, making it seem like it did not upload a copy of the file:

Server team confirmed that only 50% of the 300GB is being used.

Running for the first time on the server appears to have no issue:

Re: File Input message 0 records were read from file (limit reached)

JoeS — Fri, 21 Jun 2019 07:55:50 GMT

@MJ

You are right, sorry, I missed the part where you said it was on the validation run that this occurred.

The validation run checks for access to the files/tables etc but doesn't need to read any records in order to validate that part, this is why you then see the limit being reached.

When you run the workflow properly it should then read them all :-)