Hey, this bug still hasn't been addressed. I am still dealing with this problem and I understand that the My Encounters portion of dndbeyond is still in beta, but the bugged encounter takes up a slot in my limited space. I am not too concerned by a single slot being used up, but I am concerned with more slots being filled with corrupted encounters.
Any advice would be very appreciated. Also, more annoying than anything, the encounter is completely unable to be edited. The date of the last save is corrupted as well, displaying Dec. 31, 1969 at 6:00 PM when I enter the Encounter. The title also displays Untitled Encounter, despite having a different title in My Encounters.
This is a known current issue that can sometimes be solved independently, though occasionally requires contacting support. See the post below by Sorce:
1 - The encounter does not have a name (so is called Untitled Encounter). To resolve this, name the encounter, and then it should delete. (0.00001% of the time an unnamed encounter can fall into category 2)
2 - The encounter does have a name and cannot be deleted. To resolve this, you will need to raise a Support Ticket, as we need the dev team to run the rebuild tool on these encounters. When raising a Support Ticket (http://dndbeyond.link/SubmitTicket), be sure to select in the form that the issue is related to Encounter Builder, include your Username/Nickname and please include the Name(s) of the encounter and the URL(s).
This is a known current issue that can sometimes be solved independently, though occasionally requires contacting support. See the post below by Sorce:
1 - The encounter does not have a name (so is called Untitled Encounter). To resolve this, name the encounter, and then it should delete. (0.00001% of the time an unnamed encounter can fall into category 2)
2 - The encounter does have a name and cannot be deleted. To resolve this, you will need to raise a Support Ticket, as we need the dev team to run the rebuild tool on these encounters. When raising a Support Ticket (http://dndbeyond.link/SubmitTicket), be sure to select in the form that the issue is related to Encounter Builder, include your Username/Nickname and please include the Name(s) of the encounter and the URL(s).
Thanks for the reply Halfwing. How do we rename the encounter, though? Attempting to click "edit" in the encounter menu takes me to a fresh encounter creation screen which seems to have no connection to the encounter I'm trying to edit. (e.g. naming that encounter and hitting 'save changes' just creates a new encounter and doesn't let me delete the bugged one).
This behavior sounds like case number 2, which will require Support to manually delete for you. In the event of an unnamed encounter falling under case number 1 (rename to delete), renaming the encounter would result in a renamed encounter that is ready to delete.
As the title says, i have some encounters that i just can't remove. I have tried every way i can imagine. Deleting it from the encounter list, trying to run the encounter (which now just loads, nothing in it and can't edit it) and then removing it there, to no success. Anyone else had this issue?
It has been a common enough issue, although I believe the underlying cause has been fixed for newly created encounters, but perhaps not those created before the issue was tracked down. In any event, try these solutions in order:
-Make sure the encounter and the campaign it is related to have names
-If that doesn’t resolve it, follow the steps from IAmSposta here.
-If that doesn’t do it, file a support ticket following the instructions here.
I've got the same issue, have raised a support ticket with the information. There are 2 different encounters. Both are named and both are related to the same campaign.
Sent a ticket, my encounter is named and has all info, yet when you open it it's empty and it creates a new one. I'm a bit concerned regarding the fact that this seems to be a recurrent issue and the dev response has been "just create a support ticket".
They should make sure encounters come with a default set of info if the name or any other vital info is empty, or fill them before deletion. I complain a lot in my forum posts, but I like this site and I pay a master tier every month, I feel like the customer relationship side of the product is lacking guys.
A better communication would be: 1. We HEAR you regarding the problem and we're sorry you're experiencing it 2. As a TEMPORARY fix, send us a support ticket and we'll take care of it 3. We're looking for a SOLUTION we'll SHARE with you, so your feedback is helpful/appreciated 4. Solution can be expected in days/months/years according to the priority this has over development of current features
Sent a ticket, my encounter is named and has all info, yet when you open it it's empty and it creates a new one. I'm a bit concerned regarding the fact that this seems to be a recurrent issue and the dev response has been "just create a support ticket".
They should make sure encounters come with a default set of info if the name or any other vital info is empty, or fill them before deletion. I complain a lot in my forum posts, but I like this site and I pay a master tier every month, I feel like the customer relationship side of the product is lacking guys.
A better communication would be: 1. We HEAR you regarding the problem and we're sorry you're experiencing it 2. As a TEMPORARY fix, send us a support ticket and we'll take care of it 3. We're looking for a SOLUTION we'll SHARE with you, so your feedback is helpful/appreciated 4. Solution can be expected in days/months/years according to the priority this has over development of current features
Given the number of times Sorce in particular has responded in this thread, I think they’ve met #1 and #2. See this post which I regard as falling under #3 and part of #4.(Though I will grant you, a more clear “thank you everyone for the info that has helped us identify us” would have been helpful.). In terms of the ETA part of #4, unless they drastically change policy, that won’t be happening. They’ve clearly said they don’t provide ETAs. Although in this case, as far as they can tell, the issue is fixed for any campaigns created after they worked out the fix.
Unfortunately, there are a few different sub issues all tied into a general "can't delete" problem; most of them have been resolved, however it isn't something we can mass fix for encounters that had the issue - and the only way to mass fix this to never come up is to mass delete everyone's encounters. As that isn't an option, the only thing we can offer to do is process through the rebuild tool, which in turn will delete the encounter once the fix has been applied. (And trust me, I did ask for any way we could mass rebuild, update, and it just isn't possible without potentially users losing encounters at random which is not a route any of us want to go down unless it is our only option)
There isn't any ongoing update to provide, other than, when you find an encounter you cannot delete, try the methods posted or raise a ticket to remove. I'm sorry if this thread seems like it seems like it is an ongoing development update, the root causes the team have discovered and resolved, but the onflow effects will continue to impact.
It has been multiple years are there still no fixes.
I thought that Sorce's response (below for reference) explained that there is a fix, but that it can't be mass applied or people would lose their data. Can you imagine the outrage that 'losing data/encounters' would cause even if it was 'implementing a fix'? From Sorce's comment, it looks like they are actioning requests as quickly as possible whenever there is an issue by running their rebuild tool.
From personal experience (I had to send in a report to get this resolved) it was fixed very quickly with no issue to any of my other encounters. There wasn't really any drama with it.
Unfortunately, there are a few different sub issues all tied into a general "can't delete" problem; most of them have been resolved, however it isn't something we can mass fix for encounters that had the issue - and the only way to mass fix this to never come up is to mass delete everyone's encounters. As that isn't an option, the only thing we can offer to do is process through the rebuild tool, which in turn will delete the encounter once the fix has been applied. (And trust me, I did ask for any way we could mass rebuild, update, and it just isn't possible without potentially users losing encounters at random which is not a route any of us want to go down unless it is our only option)
There isn't any ongoing update to provide, other than, when you find an encounter you cannot delete, try the methods posted or raise a ticket to remove. I'm sorry if this thread seems like it seems like it is an ongoing development update, the root causes the team have discovered and resolved, but the onflow effects will continue to impact.
Sorce, just a quick question - once your team has run the 'rebuild tool' does that mean that the issue won't occur again on that account? Just curious.
It has been multiple years are there still no fixes.
Umm, no it has not been multiple years. The first post in this thread is dated to May 2021 and the first trouble report to be found on the thread is in July. Also, as RickiSparks explained, there is an available fix.
We run the rebuild against the specific encounter ID. Because the issue was sporadic across encounters, there isn't any way to determine which encounters might not delete until someone attempts to delete them. There shouldn't be problems with newer encounters, however there could be, which is why I added the first post (the issue wasn't actually first reported until July last year, but to have the first post, I needed to pull a comment I had on another thread and merge here, aka forum wizardry at its finest).
I'm unable to delete the below encounter. When I'm just looking at the encounters it is named, Doppelganger in Roxbalt. When I enter into it though, it says Untitled Encounter. I tried to use the link in your first post to submit a ticket, http://dndbeyond.link/SubmitTicket, I got a "This site can't be reached" error.
Hey, this bug still hasn't been addressed. I am still dealing with this problem and I understand that the My Encounters portion of dndbeyond is still in beta, but the bugged encounter takes up a slot in my limited space. I am not too concerned by a single slot being used up, but I am concerned with more slots being filled with corrupted encounters.
Any advice would be very appreciated. Also, more annoying than anything, the encounter is completely unable to be edited. The date of the last save is corrupted as well, displaying Dec. 31, 1969 at 6:00 PM when I enter the Encounter. The title also displays Untitled Encounter, despite having a different title in My Encounters.
Also having this issue and made a separate post about it. Here's my post on it with encounter IDs: https://www.dndbeyond.com/forums/d-d-beyond-general/bugs-support/130520-broken-encounter#c2
This is a major bug because it could make the encounter designer potentially unusable for some people. Please provide support!!
-
View User Profile
-
View Posts
-
Send Message
AlumniThis is a known current issue that can sometimes be solved independently, though occasionally requires contacting support. See the post below by Sorce:
Thanks for the reply Halfwing. How do we rename the encounter, though? Attempting to click "edit" in the encounter menu takes me to a fresh encounter creation screen which seems to have no connection to the encounter I'm trying to edit. (e.g. naming that encounter and hitting 'save changes' just creates a new encounter and doesn't let me delete the bugged one).
-
View User Profile
-
View Posts
-
Send Message
AlumniThis behavior sounds like case number 2, which will require Support to manually delete for you. In the event of an unnamed encounter falling under case number 1 (rename to delete), renaming the encounter would result in a renamed encounter that is ready to delete.
Alright, thanks for the help. I'll post a ticket.
As the title says, i have some encounters that i just can't remove. I have tried every way i can imagine. Deleting it from the encounter list, trying to run the encounter (which now just loads, nothing in it and can't edit it) and then removing it there, to no success. Anyone else had this issue?
It has been a common enough issue, although I believe the underlying cause has been fixed for newly created encounters, but perhaps not those created before the issue was tracked down. In any event, try these solutions in order:
-Make sure the encounter and the campaign it is related to have names
-If that doesn’t resolve it, follow the steps from IAmSposta here.
-If that doesn’t do it, file a support ticket following the instructions here.
Trying to Decide if DDB is for you? A few helpful threads: A Buyer's Guide to DDB; What I/We Bought and Why; How some DMs use DDB; A Newer Thread on Using DDB to Play
Helpful threads on other topics: Homebrew FAQ by IamSposta; Accessing Content by ConalTheGreat;
Check your entitlements here. | Support Ticket LInk
I've got the same issue, have raised a support ticket with the information. There are 2 different encounters. Both are named and both are related to the same campaign.
Sent a ticket, my encounter is named and has all info, yet when you open it it's empty and it creates a new one. I'm a bit concerned regarding the fact that this seems to be a recurrent issue and the dev response has been "just create a support ticket".
They should make sure encounters come with a default set of info if the name or any other vital info is empty, or fill them before deletion. I complain a lot in my forum posts, but I like this site and I pay a master tier every month, I feel like the customer relationship side of the product is lacking guys.
A better communication would be:
1. We HEAR you regarding the problem and we're sorry you're experiencing it
2. As a TEMPORARY fix, send us a support ticket and we'll take care of it
3. We're looking for a SOLUTION we'll SHARE with you, so your feedback is helpful/appreciated
4. Solution can be expected in days/months/years according to the priority this has over development of current features
Given the number of times Sorce in particular has responded in this thread, I think they’ve met #1 and #2. See this post which I regard as falling under #3 and part of #4.(Though I will grant you, a more clear “thank you everyone for the info that has helped us identify us” would have been helpful.). In terms of the ETA part of #4, unless they drastically change policy, that won’t be happening. They’ve clearly said they don’t provide ETAs. Although in this case, as far as they can tell, the issue is fixed for any campaigns created after they worked out the fix.
Trying to Decide if DDB is for you? A few helpful threads: A Buyer's Guide to DDB; What I/We Bought and Why; How some DMs use DDB; A Newer Thread on Using DDB to Play
Helpful threads on other topics: Homebrew FAQ by IamSposta; Accessing Content by ConalTheGreat;
Check your entitlements here. | Support Ticket LInk
Thank you for the summary kind soul.
Unfortunately, there are a few different sub issues all tied into a general "can't delete" problem; most of them have been resolved, however it isn't something we can mass fix for encounters that had the issue - and the only way to mass fix this to never come up is to mass delete everyone's encounters. As that isn't an option, the only thing we can offer to do is process through the rebuild tool, which in turn will delete the encounter once the fix has been applied. (And trust me, I did ask for any way we could mass rebuild, update, and it just isn't possible without potentially users losing encounters at random which is not a route any of us want to go down unless it is our only option)
There isn't any ongoing update to provide, other than, when you find an encounter you cannot delete, try the methods posted or raise a ticket to remove. I'm sorry if this thread seems like it seems like it is an ongoing development update, the root causes the team have discovered and resolved, but the onflow effects will continue to impact.
Site Rules & Guidelines || How to Tooltip || Contact Support || Changelog || Pricing FAQ || Homebrew FAQ
If you have questions/concerns, please Private Message me or another moderator.
Wary the wizard who focuses on homebrew, for he can create nightmares that you wouldn't even dream of
Yeah I thought by reading the post that it was an ongoing development. Anyway thank you Sorce for the clarification.
It has been multiple years are there still no fixes.
I thought that Sorce's response (below for reference) explained that there is a fix, but that it can't be mass applied or people would lose their data. Can you imagine the outrage that 'losing data/encounters' would cause even if it was 'implementing a fix'? From Sorce's comment, it looks like they are actioning requests as quickly as possible whenever there is an issue by running their rebuild tool.
From personal experience (I had to send in a report to get this resolved) it was fixed very quickly with no issue to any of my other encounters. There wasn't really any drama with it.
Sorce, just a quick question - once your team has run the 'rebuild tool' does that mean that the issue won't occur again on that account? Just curious.
Umm, no it has not been multiple years. The first post in this thread is dated to May 2021 and the first trouble report to be found on the thread is in July. Also, as RickiSparks explained, there is an available fix.
Trying to Decide if DDB is for you? A few helpful threads: A Buyer's Guide to DDB; What I/We Bought and Why; How some DMs use DDB; A Newer Thread on Using DDB to Play
Helpful threads on other topics: Homebrew FAQ by IamSposta; Accessing Content by ConalTheGreat;
Check your entitlements here. | Support Ticket LInk
We run the rebuild against the specific encounter ID. Because the issue was sporadic across encounters, there isn't any way to determine which encounters might not delete until someone attempts to delete them. There shouldn't be problems with newer encounters, however there could be, which is why I added the first post (the issue wasn't actually first reported until July last year, but to have the first post, I needed to pull a comment I had on another thread and merge here, aka forum wizardry at its finest).
Site Rules & Guidelines || How to Tooltip || Contact Support || Changelog || Pricing FAQ || Homebrew FAQ
If you have questions/concerns, please Private Message me or another moderator.
Wary the wizard who focuses on homebrew, for he can create nightmares that you wouldn't even dream of
I was having the issue listed under #1.
I named the encounter "Delete Encounter". When I did this it created a new encounter. Now I can't delete either one.
I'm opening a ticket to resolve now.
Hello,
I'm unable to delete the below encounter. When I'm just looking at the encounters it is named, Doppelganger in Roxbalt. When I enter into it though, it says Untitled Encounter. I tried to use the link in your first post to submit a ticket, http://dndbeyond.link/SubmitTicket, I got a "This site can't be reached" error.
https://www.dndbeyond.com/encounters/b84c7a8d-2bba-4b89-b95e-1bd8a5673216