Like the title says. I've set the automation to send a follow up tag if a response is not submitted by the ticket owner within 30 minutes. I've tested this and sent a response but the tag still triggers.
#Automation [watcher[ check for message (is not found in x time) not working.
vestal barn
jovial dagger
Like the title says. I've set the automation to send a follow up tag if a respon...
Can I get your server id?
And is Buck the owner of the ticket?
the one who created it?
jovial dagger
Like the title says. I've set the automation to send a follow up tag if a respon...
Actually. I'm confused, it looks like it worked just fine?
it would 30 minutes of no response before sending the ping.
@vestal barn
vestal barn
it would 30 minutes of no response before sending the ping.
Yes and the ping still triggered even though a message was already sent to the ticket >30 mins.
jovial dagger
Yes and the ping still triggered even though a message was already sent to the t...
Can I get your server id?
I want to check on the configs
vestal barn
1042760825024286770
vestal barn
And is Buck the owner of the ticket?
Yes.
vestal barn
Ah yes, I deleted it after doing the test. Would you want me to recreate it again with automation left on?
I tested it on a live ticket, didn't want customers being pinged even though they provided the information we requested already so I turned it off.
jovial dagger
Ah yes, I deleted it after doing the test. Would you want me to recreate it agai...
Did you ever turn on advanced?
vestal barn
Oh I did not, I assumed it would work w/o it
jovial dagger
Oh I did not, I assumed it would work w/o it
It does
I was wondering if you changed any of the advanced options.
vestal barn
I didn't. It was a new automation since I deleted the old one (the one I noticed the bug on before I remade an automation for testing)
jovial dagger
Like the title says. I've set the automation to send a follow up tag if a respon...
Did you send that message pretty immediately after creating the ticket?
vestal barn
Around a minute after creation
jovial dagger
ok, yeah, that checks out.
Under advanced there's an option to have it only check once.
Instead of every 30 minutes.
vestal barn
jovial dagger
Though I think you might be right about it having issues.
jovial dagger
Lets see..
Created ticket: 5:52
Sent Message: 5:43 (1 minute)
Automation triggered: 6:12 (29 minutes)
Didn't detect ticket owner..
jovial dagger
I'm going to download my logs and see what happened.
currently the automation is in alpha testing, and we have noticed some odd results like this.
vestal barn
1068836318014087229
jovial dagger
First image one or 2nd one?
vestal barn
1068836318014087229
The one with Bucky I deleted already
Made it only for screenshotting purposes
jovial dagger
Do you have this one also?
vestal barn
Wdym?
jovial dagger
Channel id
vestal barn
1068836318014087229
This is the channel ID
jovial dagger
1068836318014087229 = Bucky ticket
??? = Smiling ave ticket
Larger sample size helps narrow down the issue.
vestal barn
Deleted = Bucky ticket
1068836318014087229 = Smiling ave ticket
I wasnt able to get the channel ID for bucky before deleting
Kidding
I have transcripts automatically on
Wait let me check logs
Bucky: 1068828464637018112
Smiling Ava: 1068836318014087229
vestal barn
jovial dagger
<a:GideonSpecial:553728624893624366>
Looks like there might be a bug here
I'll start the investigation on my side with some more testing.
vestal barn
I've tested again though this time something weirder happened. The trigger was called 30 minutes after ticket owner sent a message.
Ticket Create: 1:57AM
First Message: 2:03AM
Trigger: 2:33AM
Channel ID: 1068952982256894073
vestal barn
jovial dagger
I've tested again though this time something weirder happened. The trigger was c...
Found out it wouldn't detect messages sent in the first 30s of the tickets life.
My test is showing good results
vestal barn
Great!
vestal barn
got it
jovial dagger
I've tested again though this time something weirder happened. The trigger was c...
And for this one, if you have restart timer enabled, it will restart the timer anytime x user sends a messages.
so instead of checking 30 minutes after the ticket was created only, it will restart the timer and check 30 minutes after that instead.
Only want restart if you plan to have the check repeating.
On an update to the dashboard (Not released yet) it actually addresses this and hides the other options when once and stop is selected.
And I've just released an update to fix this bot side.
vestal barn
It's working perfectly now