error (syntax error: Unexpected token p)

[DivisionVapor]

response is a string
caught an error: [SyntaxError: Unexpected token p]
vend.js - sendRequest - An unexpected error occurred: [SyntaxError: Unexpected
token p]
generate-stock-order-divisionvapor > An unexpected error occurred: [SyntaxError
: Unexpected token p]
finished stock ordering process for: b8ca3a65-01a6-11e4-fbb5-3a0a75ce5df2
orders across all the applicable outlets were created

I ran an order for all stores (2 stores) and it only produced an order for one store. The other store didn't have an order.

[pulkitsinghal]

I can reach out for a quick screenshare and call at 4pst, is that ok?

This is new? Meaning the error hasn't happened all the times u used until now?

Sent from my iPhone

[DivisionVapor]

Just happened today. Pretty sure it happened twice. The first time it ran it only pulled up one store. I thought maybe it just meant that I didn't need to order anything for one store. On the second run I increased to 6w interval (first time) and ran it again. This time it again only ordered for one store and I saw the error when I went back over it.

[pulkitsinghal]

Thanks for the info. Can you confirm your availability for a 4pm pst call?

Sent from my iPhone

[DivisionVapor]

Can't confirm yet. I'll let you know in an hour or so. I'm running a bunch of orders right now and they seem to be working fine. I'm wondering if I had an internet connection error and that produced the error.

[DivisionVapor]

I've run more orders today than any other day. Once I got the internet a little more stable, I haven't seen the problem again. Does that look like an error a bad internet connection would cause?

[pulkitsinghal]

I think it might be possible for the error to be caused by poor internet connection. I would feel a whole lot better if this was something that I could reproduce on my side and then make it so that it stated clearly that an internet connection is the problem ... if that is indeed the issue at the heart of it.

[pulkitsinghal]

What would help me is if next time this happens, you can copy/paste the ENTIRE log from start to end into a file and then ship it to me for a look. If you can't meet today or you can't reproduce the problem anymore today then that should be our strategy for the next time it happens. We can keep this issue open. Thoughts?

[DivisionVapor]

I'll keep an eye on it and see if it happens again. Go ahead and close the issue though, I'm now fairly certain it was probably caused by a time out issue that really didn't display.