Legacy Dev Forum Posts

 View Only

Sign Up

Terraform failing for callback option during Queue creation

  • 1.  Terraform failing for callback option during Queue creation

    Posted 06-05-2025 18:30

    Aslam_Ahamed | 2024-04-18 17:22:26 UTC | #1

    We are using Terraform provider version 1.36.1 and have included media_settings_callback options for callback auto dial and end.

    On apply, Queue object is getting created with all options set for callback but the provider throws an error.

    Below is out queue object settings and the error seen from terraform apply.

    resource "genesyscloudroutingqueue" "TestCallbackQueue" { mediasettingschat { enableautoanswer = false enableautodialandend = false serviceleveldurationms = 20000 servicelevelpercentage = 0.8 alertingtimeoutsec = 30 } scoringmethod = "TimestampAndPriority" enablemanualassignment = false enabletranscription = true queueflowid = data.genesyscloudflow.InQueueFlow.id suppressinqueuecallrecording = false whisperpromptid = data.genesyscloudarchitectuserprompt.whisperFunding2.id agentownedrouting { maxownedcallbackhours = 2 enableagentownedcallbacks = false maxownedcallbackdelayhours = 2 } mediasettingscall { enableautoanswer = false enableautodialandend = false serviceleveldurationms = 20000 servicelevelpercentage = 0.8 alertingtimeoutsec = 8 } skillevaluationmethod = "ALL" skill_groups = []

    callingpartyname = "Via Benefits Cloud Dev" mediasettingsemail { alertingtimeoutsec = 300 enableautoanswer = false enableautodialandend = false serviceleveldurationms = 86400000 servicelevelpercentage = 0.8 } mediasettingsmessage { serviceleveldurationms = 20000 servicelevelpercentage = 0.8 alertingtimeoutsec = 30 enableautoanswer = false enableautodialandend = false } autoansweronly = false defaultscriptids = { } name = "TestCallbackQueue" acwwrapupprompt = "OPTIONAL" mediasettingscallback { enableautodialandend = true autodialdelayseconds = 10 autoenddelayseconds = 1 serviceleveldurationms = 20000 servicelevelpercentage = 0.8 alertingtimeoutsec = 30 enableautoanswer = true } divisionid = data.genesyscloudauthdivision.Home.id }

    Error from terraform apply:

    genesyscloudroutingqueue.TestCallbackQueue: Still creating... [4m50s elapsed] genesyscloudroutingqueue.TestCallbackQueue: Still creating... [5m0s elapsed] ╷ │ Error: mismatch on attribute mediasettingscallback.0.enableautodialandend: │ expected value: <nil> │ actual value: true │ │ with genesyscloudroutingqueue.TestCallbackQueue, │ on Testcallbackqueue.tf line 32, in resource "genesyscloudroutingqueue" "TestCallbackQueue": │ 32: resource "genesyscloudroutingqueue" "TestCallbackQueue" {


    Hemanth | 2024-04-19 18:24:40 UTC | #2

    AslamAhamed, post:1, topic:25806
    enableautodialand_end

    Hi @Aslam_Ahamed Thanks for bringing this to notice. We will fix the problem and update you. You can still use the terraform resource queue as the callback option mentioned is an optional parameter .

    Thankyou.


    Aslam_Ahamed | 2024-05-01 21:55:15 UTC | #3

    Hi Hemanth,

    Any update on when we will have a fix for the the optional parameters for callback start and end through terraform.

    We have a major changes to our huge list of 600 queues to update with these callback settings through terraform before our Go-Live.

    Let us know tentative date on this so we can plan our updates either through terraform or manually update on all 600 queues.

    Thanks, Aslam


    Hemanth | 2024-05-02 08:43:56 UTC | #4

    Hi @Aslam_Ahamed

    The latest version https://registry.terraform.io/providers/MyPureCloud/genesyscloud/latest have fix for this problem. Can you run your app , with this provider and let us know if it resolves the problem.

    Thanks Hemanth


    Aslam_Ahamed | 2024-05-02 21:45:03 UTC | #5

    Hi @Hemanth

    I tried with latest version 1.37.0 and are able to update all our queues with mediasettingscallback options successfully.

    Thanks Aslam


    system | 2024-06-01 21:45:51 UTC | #6

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


    This post was migrated from the old Developer Forum.

    ref: 25806