I have built a flow for my application to verify the logic, but I am encountering a problem in one of the blocks. Is there any way I can share that diagram here as a PDF or high-resolution image so that you can check everything in detail? Taking a screenshot is not a very convenient way to present the flow.
Hi @Artyomsv
While we don’t have this feature today, we are working on something that will allow you to share flow diagrams in the future.
If you’re running into an issue that’s difficult to present with screenshots, you can either try to explain the issue you’re encountering here and I can see if it sounds like something i’ve seen before or send me a DM and we can setup a screen-share call if that works for you.
Thanks for your reply. I think it will be better to have this discussion here in case others may have a similar issue.
I`ve combined multiple screenshots into a single large jpg, hopefully, it will be readable.
My application flow is following:
- Create an interview session object
- Get the list of assigned question
- Get assigned question
- Post answer
- repeat steps 2-4 till step 2 has one of the boolean flags in the response body as false.
The issue is that the first round works just fine, but the second stops somewhere between red and orange blocks and I cannot understand why.
the image was cropped 
Here is the problematic part, I hope in better resolution:
In my experience when you have a loop and it doesn’t run the second time, there’s a connection that isn’t generating data. I can’t make out the entire graph enough to see where that might be happening in your flow (Great use case, are you using AI at all here?) but I can tell you in about a week you’ll be able to share your flow in a much better way.
In the meantime, here’s something to check, do you have any literal blocks that are part of the loop? These blocks only provide a value once - save them to a variable and use the pin behavior. If this doesn’t apply, check that ports that are part of the loop have data being generated also on the loop back edge.
(We know this is a not a great experience and it’s top of mind for us to fix so that loops like this are easier to understand, debug, and get right more quickly.)