Getting error on save

Get Help
1

Every time I toggle the slack node to act as a trigger I get an error when attempting to save. This does not occur when the slack node is not a trigger.

Here’s a run link: https://www.gumloop.com/pipeline?run_id=2xTeTkgvFHwUo85CwEKYFL&workbook_id=ufZnvtwqGWpc5WHgReZHcC

2

Hey @northbagel! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.

  1. Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}

  2. Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
    GIF guide

  3. Provide details about the issue—more context helps us troubleshoot faster.

You can find your run history here: https://www.gumloop.com/history

3

Hey @northbagel – Could you please try the following steps AFTER clearing cookies and logging in again:

  1. Disable the trigger on the node.
  2. Click the refresh icon next to the channel name dropdown.
  3. Select the channel again.
  4. Enable the trigger and save.
  5. Try making any edits while the trigger is active to see if the save function works.

Let me know if that works for you.

4

Cleared cookies and logged in again, also following the steps to disable and refresh.

I’m still getting the same error. Able to save when the trigger is disabled, not able to when its enabled.

5

That’s strange but thank you for trying. Do you mind sharing access by adding my email (wasay@gumloop.com) or setting the workbook to “anyone with the link can view” from the share button please?

image
image1378×710 22.6 KB

I’ll create a ticket to investigate this further and keep you posted.

6

Added you! Thank you.

7

Great, thanks! I’ve created a ticket for this.

8

@northbagel – @mike – Could you confirm if the Gumloop bot is in the Slack channel?

To add the bot, you have two options:

  1. Type /invite @Gumloop in the channel, OR
  2. Click the channel name → Add integrations/Add app → Search for “Gumloop”

Once you add the bot the trigger should work as expected, let me know.

9

Thanks, i’ve added the gumloop bot to the channel, refreshed, but it still won’t save when the node is enabled as a trigger. But it will when its not.

10

Noted, thank you! I’ve created a ticket to investigate this further. Will keep you posted.

11

Thank you!

12

Hey @northbagel – We pushed a fix for this, could you please delete and add back the Slack Reader node and then test it out please? Really appreciate your patience here!

13

Thank you! It’s now working on my end. Appreciate the quick fix!

14

I’ve been testing the trigger, and while it can now save (previously it couldn’t) I haven’t been able to get the trigger to initiate. I send a message in the slack channel linked up to the trigger and the run does not start.

15

Just to confirm, you’re checking the triggered runs on the https://www.gumloop.com/history page or through the previous runs tab correct?

image
image3840×780 96.3 KB

If you’re not seeing any triggered runs there, could you please try the following:

  • Disable the trigger on the Slack node and save the workflow
    • Once you save, you’ll notice the trigger would disappear from the top panel
  • Once the trigger is disabled, delete the Slack node and add it back from the node library
  • Enable the trigger and hit save
    • You’ll notice the trigger would appear on the top panel

If this doesn’t work could you please try revoking and authenticating with Slack again, once that is done please try the above steps again.

16

Thanks for the help.

Yes, i’ve checked the history - not seeing any triggered runs.

I’ve gone through the steps provided. I can manually run the workflow and it successfully pulls Slack messages through the workflow. However, the trigger does not work automatically.

17

Got it, thank you! Looking into this further..

18

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.