And what is the purpose of the scenario, exactly? Can you explain it step by step?
The HTTP module is by default synchronous; It will wait for the external APIs’ response before it can parse the result into bundles. In general, HTTP requests can be asynchronous, but not in the context of Make. That is not how it works in Make.
With synchronous HTTP calls (from Make), regarding the type of job and its severity, the job can take too long. This might cause a timeout (default 40 sec). E.g. with file conversion such as CloudConvert. In that case, it is better to create two scenario’s:
- Will start the asynchronous process through a HTTP call
- Will wait for incoming requests whenever a asynschronous process ends, here you can process the results as you like.
I think this is sort of what you are trying to do with the sleep modules? It would be better to have a second scenario that runs whenever the answer in Relevance.ai is ready (I am not familiair with this tool)
Cheers,
Henk