Workflow Shows Success on App Before Actually Finishing Running

💬 Workflows
21

Hi @Toatzin_Padilla Thanks for reaching out! Very strange that it broke :disappointed: I don't see any known branch block issues (a similar workflow is working on my side), but maybe this is an edge case. Could we see the branch logic? or could you share an export of the workflow?

22

+1

23

Any updates? The problem is still accuring

24

We should have a fix soon! :blush: I will post here when I see that it has been shipped

25

Is this fixed ?

26

Any update? This becomes really an issue

27

+1, waiting for the fix

28

I'm see the same error. Is there a fix?

1 Like
29

The bug fix shipped to Cloud! Are folks still seeing issues?

30

@Tess, I am personally still having this issue indeed,

  1. We call the workflow as follows

    image
    image535×526 24.1 KB

  2. The workflow runs for 20+ Seconds
    image

  3. The (workflowhere).isFetching method finishes in less than a second and our logs show the same; despite the workflow still running
    image

Version reference
image

31

Hi @Chris_Firgaira,

Thanks for reaching out. :thinking: I haven't been able to reproduce this yet. Can you also share an export of the workflow or a screenshot of the return block?

Just to confirm, the workflow logs show that the return block successfully returns valid json?

32

Hey @Tess

Do you have an email I can send the workflow too? Just mindful we haven't utilised variables just yet and are probably exposing some passwords :slight_smile: that I need to tidy up before sharing

Where should I take a screenshot of the return block sorry?

This is an example of a button we pressed that invokes a workflow, it returns .6 seconds and the following data in console
image

Subsequently we can see the workflow ran for 150 seconds
image

Also, we're not asking our workflow to return a JSON presently, was just wondering to monitor for it's state to be complete so we can provide a notification to user of

  1. When the workflow is still running
  2. When it completes
  3. Trigger a query to run

What screenshots would you like me to share to better support this process? Also, any tips on where we should store our API passwords to remove them from our workflow for sharing?

33

Hi @Chris_Firgaira,

You are welcome to send me a direct message here on the forum! But without a JSON return block, the workflow will run in a "fire and forget" asynchronous manner, and will not wait for the workflow to finish before returning completed to the App.

You could return some dummy data in your workflow in order to accomplish your use case

34

Thanks so much Tess!

I wonder if others were as clueless as me! I needed to create a "response" block. Much appreciated, had no idea that would have been the cause of "Fire and forget" operation, much to learn over here many thanks again!

image

1 Like