Thanks again James,
Yes, the Create new Rephrase is just to investigate the issue.
The taskID is necessary for the API. The initial workflow is: User types in input–>POST request to API with input–>API immediately responds back with taskID–>Input and taskID stored in database–> API processes input (There is significant delay in processing the input, which is why I use a taskID through celery in my API)–> when API is finished processing, send POST request using backend workflow to bubble with the taskID and output.
There are scenarios where the app could be handling multiple tasks at once, so the taskID (I think) is necessary to keep the inputs and outputs in sync.
I would like to investigate further if I am triggering my backend workflow before the task, but I’m not sure that’s possible. To my knowledge, the backend workflow only triggers when the POST request comes in from my API. Given that there is a delay of at least a couple seconds that it takes my API to process, I don’t see how thats possible. The API doesn’t send the POST request until processing is finished. Also, when i troubleshoot using the Create a new thing, I can see the initial task get created, and then after a few seconds, the new thing appear in the database.
Thanks so much again for your help!