Genesys Cloud - Main

 View Only

Sign Up

  • 1.  Tip: using a data table as a lock for scheduled workflows

    Posted 6 days ago

    For an hourly workflow, we use a data table row with a timestamp as a simple lock, so a trigger and a scheduled run don't act twice within 60 minutes. Curious how others handle concurrency in workflows. Do you use data tables, or something else?


    #ArchitectandDesign

    ------------------------------
    Vinicius
    ------------------------------


  • 2.  RE: Tip: using a data table as a lock for scheduled workflows

    Posted 5 days ago
    Edited by Phaneendra Avatapalli 5 days ago

    Hi Vinicius,

    We use a data table to track the count and timestamp for a workflow triggered when an agent enters Not Responding. It was initially set to stop after three resets to Idle, but the business later wanted the workflow to return the agent to Idle every time, so we removed that cap. It’s not a concurrency lock, but it shows how we used a data table to control how often the workflow runs.



    ------------------------------
    Phaneendra
    Technical Solutions Consultant
    ------------------------------



  • 3.  RE: Tip: using a data table as a lock for scheduled workflows

    Posted 5 days ago

    Hi Vinicius,

    In our environment, we make extensive use of Data Tables within Architect, primarily to externalise configuration and routing logic rather than hardcoding values in flows.

    We use Data Tables to control things such as queue routing, priorities, prompts, feature enablement, dynamic meeting activation, estimated wait time behaviour, and other runtime configuration. This allows us to change behaviour without having to republish flows every time a business requirement change. 

    While we're not currently using them as a workflow concurrency lock, I can see the appeal of the timestamp-based approach. Data Tables are lightweight, native to the platform, and already play a key role in how we manage dynamic behaviour across our solutions.

    It would be interesting to hear whether others are using Data Tables for concurrency control and processing-state tracking.



    ------------------------------
    Akhil
    ------------------------------



  • 4.  RE: Tip: using a data table as a lock for scheduled workflows

    Posted 3 days ago

    Hi Vinicius,

    I use data tables with timestamps, too. It's a simple way to prevent double excecutions. Only problem is, that in rare cases, writing into the data table can fail. I implemented a "send notificaton"-step for that cases to restart the workflow manually.



    ------------------------------
    Christoph
    Produktmanager Kunden-Dialog-Center
    ------------------------------



  • 5.  RE: Tip: using a data table as a lock for scheduled workflows

    Posted 3 days ago

    Hi Vinicius,

    Nice approach. Like Akhil, we don't use data tables for locking, but we rely on them in an IVR to map 233 municipalities to their outage prompts, so we can update them without republishing the flow.

    Christoph's point about write failures is a good one. Have you seen cases where two runs read the table at almost the same time, before either one updates the timestamp?



    ------------------------------
    Diego
    NA
    ------------------------------



Related Content