automaFetch not working

[SeanSobey]

I have a server running locally to provide some data to use in a workflow. Since the last update (or 2), this is no longer working.

This runs in a javascript block:

async function main() {
  
  const automaNextBlockOrig = automaNextBlock; // Since framework calls this sync, hack to wait for our async
  automaNextBlock = () => {};
  
  const {
		  legalEntity,
		  address,
		  loanDetails
  } = await automaFetch('json', { url: 'http://localhost:3041/data'});
  
  automaSetVariable('legalEntity', legalEntity);
  automaSetVariable('address', address);
  automaSetVariable('loanDetails', loanDetails);

  automaNextBlock = automaNextBlockOrig;
  automaNextBlock();
}

main();

Note the hack to wait for the async call, maybe this is related to it no longer working?

[bingren-yd]

Could you please let me know which block you used to execute the JavaScript? Was it the JavaScript block? If it’s convenient for you, could you provide a minimal, anonymized workflow that can reproduce the issue? This would help me pinpoint the problem more quickly.

By the way, if you’re using the JavaScript block, there must be an Active Tab block preceding it.

[bingren-yd]

You could try using the Http Request Block to replace the implementation of this part of the JS.

[SeanSobey]

Thanks for your reply. Here is a minimal version of the workflow:

automaFetch not working.automa.json

I think I have found the issue though. I am using this to build a SalesForce application and the workflow works fine on other sites, and used to on my SalesForce app. But it looks like there is some website code preventing this:

Running in the background won't work because I need to use automaSetVariable. I will try the http request block

[SeanSobey]

Indeed yes the HTTP request block works, and is faster:

Maybe this bug will still be helpful in finding a workaround for client side preventions?