Jerry_Jeremiah | 2024-07-09 02:09:04 UTC | #1
While importing a DBFlow with Terraform I get the following error. I have no idea what it means. Could someone give me an idea of what is wrong?
genesyscloudflow.DbFlow: Modifying... [id=9f9ffb51-5a71-43b8-bf9f-33ba2de65558] genesyscloudflow.DbFlow: Still modifying... [id=9f9ffb51-5a71-43b8-bf9f-33ba2de65558, 10s elapsed] genesyscloudflow.DbFlow: Still modifying... [id=9f9ffb51-5a71-43b8-bf9f-33ba2de65558, 20s elapsed] genesyscloudflow.DbFlow: Still modifying... [id=9f9ffb51-5a71-43b8-bf9f-33ba2de65558, 30s elapsed] │ │ Error: Flow publish failed. JobID: 67c98439-1be9-408b-bd8c-06185d15c146, tracing messages: session startup initialization for startWithAuthToken complete. Caught unhandled exception waiting for callback function returned promise to resolve. │ │ ArchSession.startWithAuthToken - Caught unhandled exception during callback function execution. Ending session. Exception info: [object Object]. │ │ ending the Session. Setting the exit code to 99.
I do have the sdk-debug logs but they don't show anything - the last thing in the log file is
DEBUG: 2024/07/09 13:28:35 === REQUEST === URL: https://api.mypurecloud.com.au/api/v2/flows/jobs/67c98439-1be9-408b-bd8c-06185d15c146?expand=messages Method: GET Headers: User-Agent: GC Terraform Provider/0.1.0 Authorization: [REDACTED] Content-Type: application/json Accept: application/json === RESPONSE === Status: 200
John_Carnell | 2024-07-09 18:08:03 UTC | #2
Hi Jerry,
Is this a consistent problem or just this one time you ran. Its definitely something we will be looking into.
Thanks, John Carnell Director, Developer Engagement
Jerry_Jeremiah | 2024-07-09 22:18:47 UTC | #3
Hi John,
It didn't happen the first couple times I did it, but for the last month or so it happens every single time. I thought it was something wrong with the DBFlow so I made it simpler and simpler and it still didn't work. I tried copying one that is already there but that didn't work either - so then I asked. The only thing I might have done between when it worked and now is get a newer version of the provider (I don't remember for sure) so I could try getting whatever the newer version is and see if that works...
Jerry
John_Carnell | 2024-07-10 00:50:13 UTC | #4
Hi Jerry,
I have our architect team looking into this too as the architect import piece that CX as Code calls is owned by them. Are you running a really long running deploy. Just curious. Also what version of the provider are using.
Thanks, John
Jerry_Jeremiah | 2024-07-10 02:11:38 UTC | #5
Hi John,
I can't use a tagged version as I have added the external organizations to it. So I just now downloaded the newest provider code and compiled it - it still creates the error.
The Terraform file isn't that big and the only items that need updating are the DBFlow and the Flow that calls it. It is just a small DBFlow.so I didn't expect an error because of the size:
Jerry
Jerry_Jeremiah | 2024-07-17 04:02:43 UTC | #6
Ok, so I did a terraform destroy and got rid of everything and then I did a terraform apply to recreate everything and that worked. When I did the apply the main DB flow had errors which it told me about and I fixed but I don't think that's the problem I had earlier because the simple DB Flow I tried when earlier didn't have anything inside and it still didn't work. So, I figure it was just confused and destroying and recreating everything instead of updating was the answer.
system | 2024-08-16 22:46:37 UTC | #7
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: 27144