Meeting summary workflow - Error with generated google doc generated

Questions
,
1

:bullseye: What is your goal?

Create in auto from transcript in MS Teams via Perplexity AI a summary in google doc and send via Gmail to the team

:thinking: What is the problem & what have you tried?

All the workflow is ok and generated an output file but the file looks empty and cannot be opened in google doc.

:clipboard: Error messages or input/output bundles

No error into the workflow.

:link: Create public scenario page

3

In the template, use {{yourvariablename}} in places you want to fill dynamically.
Use the google docs create a doc from a template.
It will identify those variables.

4

Sorry Juan but is not clear to me. Analysing the AI module, looks like no output has been generated. I dont know what i did wrong. In output–>Choices–>Message–> Content is only present the following “#” symbol.

5

Hi @Madesi88

The Perplexity AI response is returning a hash symbol (“#”) with finish reason: length. This probably indicates the model ran out of tokens (max_tokens) before completing its thought. This often happens with complex, deep-research queries, causing an abrupt cut-off.

The prompt itself has almost 9000 tokens.

Try increasing the max_tokens allowed.

@damato

6

Thanks a lot!! it worked. Which is the max token amount in one operation? (looking on internet looks like 8000). Any cost to afford to extend it? Any advice on temperature set up?

Cheers

Mario

7

Hello, sorry again to ask your help.

Run the model after a while and now getting the error when run a summary into the perplexity module :

[401]

401 Authorization Required

401 Authorization Required

openresty/1.27.4

Do you know what can be? I did not change any setting.

Module is create a chat completion.

Thanks in advance

Mario

8

Hi @Madesi88

A 401 Error is an authorization issue, as the message states. Check your credentials, reauthorize the client and try again (Credentials on Make’s left navigation bar).

If that intervention does not work, I strongly suggest you mark this thread as completed (Solution on post 4) and open a new thread, since its a different issue.

@damato