Legacy Dev Forum Posts

 View Only

Sign Up

Automating Sequence Schedules using AWS Lambda

  • 1.  Automating Sequence Schedules using AWS Lambda

    Posted 06-05-2025 18:21

    bryandelacruz | 2022-03-21 18:23:35 UTC | #1

    When creating a sequence schedule via the API it requires a version in the JSON that is unique to the sequence GUID. We have 12 sequence schedules to update weekly so we'd like to automate it. We're concerned that if someone makes a manual change using the API then the automation piece would have the incorrect version and error (409) . Is there a way to create sequence schedules without that version or a way to clear it out to 0 and start over through the API?

    What are developers using to work around the “version”: value associated with each sequence GUID has to be incremented in the request body. This is doable to some extent (1 week’s posting) but not feasible as our lambda/function is scheduled (it is automated). We have to figure out a way (keep a file/table somewhere), which version was used last week and increment from there. This doesn’t necessarily make the application very smart or scalable.


    tim.smith | 2022-03-18 21:54:30 UTC | #2

    I'm not really sure what you're asking about. Can you provide some context for how this question relates to Genesys Cloud?


    bryandelacruz | 2022-03-21 18:22:03 UTC | #3

    When creating a sequence schedule via the API it requires a version in the JSON that is unique to the sequence GUID. We have 12 sequence schedules to update weekly so we'd like to automate it. We're concerned that if someone makes a manual change using the API then the automation piece would have the incorrect version and error (409) . Is there a way to create sequence schedules without that version or a way to clear it out to 0 and start over through the API?


    bryandelacruz | 2022-03-21 18:22:52 UTC | #4


    system | 2022-04-21 18:23:43 UTC | #5

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


    This post was migrated from the old Developer Forum.

    ref: 13962