Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate for existing drafts before allowing a one off episode to be published #992

Closed
brandonhundt opened this issue Apr 10, 2024 · 1 comment · Fixed by #999
Closed
Labels

Comments

@brandonhundt
Copy link
Contributor

Jeanne let me know a few producers are creating new drafts on dates when drafts already exist, causing issues with previously targeted faked-in flights. Jeanne highlighted the following use cases:

  • producer created a new draft on a date when a draft already existed with flights targeted to it.

So, to me, possible solutions lie in a few places, but we should probably look at adding something to alert producers that a draft for "today" already exists and creating a new draft, when one already exists, may cause issues with ads.

Something like that???

@brandonhundt
Copy link
Contributor Author

Just now from Jeanne:

just wanted to surface something that just happened…. Normal Gossip launched today, it was their first ep in Podcasts, so they created a new ep and then deleted the old episode draft, which is all well and fine from a publishing side, except that we had a faked-in campaign targeted towards the old draft, which was deleted/not used to publish. So we missed a bunch of imps, but I think we’ll be ok because Melissa caught it in time. Potential solution… I think that if there a way for whoever is in Podcasts to see that there is something targeted to that ep, that might give them pause before they delete drafts, even though I know that in this case it was a little more complicated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant