One of our customer groups is quite large, so we need to send out quite a few notifications. The only workaround I can imagine right now is to have a new workflow that would figure out if the first one did it's job. If this execution limit is non-negotiable, a better developer experience would be that the workflow continued to the next step and logged a timeout error (and maybe there could even be a way to catch that a previous function did not execute successfully at some point). My main gripe with this problem is that Slack simply terminates the workflow. I imagine this problem can happen for other external APIs and use cases. The function is trimmed down to the bone, it only fires 1 request - and it's the response that takes time. We don't know exactly why, and Salesforce can't give us an exact answer. But a few times per day, it can take 30 seconds to get a response. When retrieving data from Salesforce, it's usually a very small graphql query ("give me 10 accounts" = 50 lines of json in and out). Step 3: Send slack messages to our partners, integrators, plugin developers, internal key account managers (this sometimes gives us errors).Step 2: Get the accounts from Salesforce for the relevant errors (this one gives us trouble, more details below).Step 1: Get errors from Splunk (this one is problem free) about errors that have been logged.We now have 5 different workflows consisting of 6-8 steps each, the main steps are (Almost) all customers communicate with us on a Slack connect channel. We have thousands of customers, big and small, and we want to notify them whenever we detect issues (wrong use of the APIs, payments not being processed, etc.). ecommerce payment, pos payment, recurring payment, login, etc.). We are a fin tech that offers a wide array of public APIs (e.g. functions that are notĪt least, that's how I would think about.Īre you able to share your use case ? The more developer use cases I can collect, the easier it is to convince teams to work on this problem. differentiating between a function that is responding to user interactions vs.being able to invoke these functions from each other, and.easier way of modularizing your application into functions, and.Increasing the timeout addresses this, but perhaps a different way of solving this would be a combination of: I think what you're asking for,, is an ability to run long-running compute tasks. Just increasing the timeout doesn't address this (quite reasonable, IMO) constraint. That's why in the original release of interactivity support for Slack apps, we almost always required a response to the interactivity event within 3 seconds. When an end-user does something in the Slack client, we want them to get some feedback that something happened within a reasonable timeframe. Let me state my view of this.įirst, it's important to know why Slack put into place these limitations to begin with. Invite it to a common channel, or just leave it as a DM-only tool.We are having many discussions on this topic internally. Now from the main integration page, click Add to Slack.ĥ This will open a window where you can sign in to your Slack team.Ħ Select your Slack team, then authorize the app.ħ Once you press " Authorize," Robin will connect to your Slack team automatically and can be found via the Team Directory. Scroll down & click Remove at the bottom. Locate the Slack integration and click Manage. Individual users do not need to refresh their Slack integration.įrom the web dashboard, navigate to Manage > Integrations. Note, this only needs to be done on the organizational level. We know this is not ideal and we're working on a better workaround for this. However, in order to get this functionality, the Slack integration needs to be refreshed by a Robin admin. In December 2022, we introduced a new Slack command, "/Who-is-in," that sends a summary of who all is planning to be in the office that week. Individual users do not need to refresh their Slack integration. In May 2023, we introduced a new Slack command, "/book-a-desk" that allows users to book a desk right in Slack.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |