I am trying to create custom events to build in a modular fashion, in the backed as part of API workflows. However, it seems like the return data from these events are not available within the API workflow. I’m guessing this is an order-of-operations issue. But shouldn’t the actions wait for the return data if they are being used? I had things working and then as soon as I tried to split it up to create reusable workflows (such as “sync-client”), nothing works. The return data isn’t available. What am I missing? Why bother having return data in these custom events if I cant use it?
What do you mean you can’t use it?
Make sure you’re using Return data in the custom event rather than Return data from API. Send screenshots if you’re unsure.
I reconfigured a bunch of things and it seems to be working now. I’m not sure if I was returning data from API, but the main thing I changed was I removed nested custom events. Could that have been the problem? Returning data from a nested custom event that returns data?
Another thing I changed was using conditionals “formatted as text” for scenarios instead of trying to merge 2 lists or items (one of which would be empty) and returning the first item, or instead of using “defaulting to”. The formatted as text option seems to be more reliable.
Overall I seem to be struggling with dealing with multiple scenarios and returning data from the “branches” so to speak.
Something that I would find handy is a “set variable” action which would be helpful for debugging. Is there any hack for that? Maybe just using a database item?
This topic was automatically closed after 70 days. New replies are no longer allowed.