How to Prevent a Workflow from Only Triggering and Ending Without Moving to the Node Step?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

I have a workflow that is only triggering and then ending. The workflow never moves to the Node step after triggering and shows 0ms for the workflow duration and 0 credits used. I’ve attempted to recreate this workflow but the new version won’t complete testing, much less deploy and run. Are there any standard tips for avoiding these issues?

2

I’m sorry to hear that you’re experiencing issues with your workflow. It’s possible that there might be an issue with the trigger or the Node step in your workflow. To better assist you, could you please provide more information about the trigger you’re using and the code in the Node step? In the meantime, if you continue to experience issues, please visit https://pipedream.com/support for more support options.

3

The trigger is a Custom Interval, running each day at midnight with the Cron rules: 0 0 ** ** *. The second step is Node code but it’s never running so I doubt it’s actually causing any issues. Either way, here is the code:

import axios from "axios"

export default defineComponent({
  props: {
    data: { type: "data_store" }
  },
  async run({ steps, $ }) {
    //
    const response = await axios({
      method: "post",
      url: "https://restapi1aws.marketsharpm.com/token",
      headers: { "content-type": "application/x-www-form-urlencoded" },
      data: {
        "grant_type": "password",
        "companyId": "391-1",
        "username": "redacted",
        "password": "redacted",
        "apikey": process.env.VerseMarketSharpAPIKey
      }
    })
    await this.data.set("391-1", response.data.access_token)
    //
  },
})
4

If anyone from Support can check the workflow is here: https://pipedream.com/@verse/projects/proj_oLsD7x/tree
Titled: CS: Vertex Roofing - Generate MarketSharp Token (391-1)

Update: the test finally went through for the new version.