This topic was automatically generated from Slack. You can find the original thread here.
Hey team - I am getting “RangeError Invalid time value” on a step that does not have any date or time inputs, so I’m assuming this to be an error with the underlying code for the step?
, would you mind sharing the specific action and input that you’re using?
no problem, is there a way I can grant you access to the workflow? The code step that is failing is quite large
Sent you a DM with a share link
chatted with Leo and it seems like the SOP for getting support on this would be to upgrade to Business.
My problem with this solution is that this bug only arose after I upgraded to Advanced the other day ( 2 days ago, I believe?), shelling out nearly $600 to do so. There have been no changes to this step other than some console.log() 's and some string modifications so I’m confused about what has caused this issue to arise at all.
Would you mind helping me with a one-time courtesy review of what might be happening here? I’ve provided <@U03CXTHK4RF with a share link. The step is “parse_recipe” and has a note on it.
The sudden onset and unexplainabilitly to the end user (me) kind of reminds me of Pipedream having sudden, random issues with my browser’s state the other day, which is frustrating for obvious reasons.
cc @UMT4G7E5P w/r/t policies around workflow-specific dev support
cc @UN1BV42B1 bc when consistent, these sort of experiences kill user evangelism
Sorry to hear you’re running into issues and frustrated, Drake. mentioned he saw your support ticket come in, so the team will triage from there and get back to you.
Thank you 
Hey , I looked into your code and the step is failing when it’s calling $.flow.rerun(). It’s missing some required arguments, please look at this docs. This is new, yeah? The latest deploy does not call $.flow.rerun() anywhere in the code.
Re: support options, feel free to always submit a support ticket at Support - Pipedream. In some cases where users need us to develop custom code, then we link them to the Business Plan.
Since many workflow support requests contain various complex custom code steps, it’s hard for us to triage when it’s an issue in the platform vs. a user mistake
As in this case, there was actually a change in the code, and I had to dig into the workflow
But we definitely want to give support when users get unblocked if they are suddenly faced with an error!
hope this helps
Hey noted. I had forgotten about email support, will pursue that avenue in the future.
Thanks for taking a look, and weird - when you say new code, do you mean on the PD side or my side? I believe the $.flow.rerun(); line has been in that step since prior to upgrading to Advanced, had run successfully/correctly in the past, and had been merged to Production multiple times.
I do believe that I previously merged without explicitly committing the changes - so I was presented with the correct diff and pressed merge, but I never when through the commit changes flow prior. Could this be part of the broader issue? For instance, here is the commit history in Github, which looks incorrect vs my expectation:
Testing my workflow a bit more, here is a Loom - it seems like maybe I have an issue with Github Sync?
Thanks ! Continuing here only because I’m uploading my screen recording…
Merging without committing shouldn’t be a problem — it joins all the changes into one commits and pushes to production.
I meant the $.flow.rerun() code was new to me, the last view I had that code was not present.
If you want, you can invite me to your GitHub repo to take a look — my username is andrewjschuang
Hey - thank you! Yes, and my apologies, I think I was digging deeper too soon. To be clear, there are at least two issues happening:
Issue 1 - It sounds like flow.rerun() is causing the range error due to missing params. This is no problem and I’m excited to move past that RangeError. What is weird, though, is that the RangeError seemingly came out of nowhere. I had run the workflow successfully with flow.rerun() in it multiple times, and I believe deployed it to production multiple times, with no issue. Which led me to Issue 2…
Issue 2 - When I went to confirm that I had deployed to production with flow.rerun() I found that my changes were not being logged correctly in Github, which led me to the Github Sync issue.
For next steps:
Issue 1 - I will confirm that adding the parameters fixes the flow.rerun() issue and reply here.
Issue 2 - I’ve added you to my Github repo so you can have a look and help me figure out what might be going on.
Github Sync is a very important feature to me - it’s the primary reason I wanted to upgrade to Advanced from a grandfathered Basic plan with a lot more credits. If we can get that feature working smoothly, I am hoping it will improve my experience on Pipedream quite a bit.
Hey ,
Thanks gotcha, let’s focus on issue #2 then.
Do you have these settings toggled on in your GitHub account by any chance?
GitHub will block any push that has your personal email because of this setting. It also returns an error. We weren’t surfacing this error but the team is working on a change to expose this info to the user
Currently, we don’t have an option to change the git email address to the private one GitHub gives ([something@users.noreply.github.com](mailto:something@users.noreply.github.com))
