3

I recently discovered a bug that makes it impossible to deploy subscriber triggers on Platform Events.

In my sandbox environment, the bug appears to be fixed. Yay! Unfortunately, that patch has not been rolled out to my production instance, preventing go-live. Is there a way to find out when patch releases are scheduled? Or to request an upgrade?

Adrian Larson
  • 149,971
  • 38
  • 239
  • 420

1 Answers1

2

if you find the issue in the known issue list then it gives you some details about what pods it's been deployed to thus far.

https://success.salesforce.com/issues_index

I remember back in the day SF released patches on Wednesdays. I'm not sure if that's still the case but if you're right that it's fixed in a sandbox a production patch might not be far along, unless they determine it's a release issue and then you're stuck till next release.

For what it's worth I googled all over the place to find the known issue for this one but I couldn't find it. Did you log a case with Salesforce? Sometimes the rep can find a internal timeline that's not public.

Dan Wooding
  • 3,518
  • 7
  • 39
  • 84
  • Sandbox was patched more than seven days ago, I believe. I'm not sure they did ever post a Known Issue. :( – Adrian Larson Jul 11 '17 at 20:43
  • Do you have a bug number or issue number? I know some T3 people who know some people. – Dan Wooding Jul 11 '17 at 20:44
  • You can see it in the comments on the linked post. Apparently it was fixed in Patch 10.0 though...hmm. Maybe they reverted the fix or something... – Adrian Larson Jul 11 '17 at 20:46
  • Strange, the patch says 10.0 but on the side it says patch 12.4 or 12.5 which if you go to that url https://success.salesforce.com/issues_releases_view?release=208012400 it says not deployed... – Dan Wooding Jul 11 '17 at 20:56
  • I think you meant https://success.salesforce.com/issues_releases_view?release=208012004 – Adrian Larson Jul 11 '17 at 21:06
  • Ha good catch, I checked with my friend best advice is reopen the support case or log a new one that's it's not fixed at least you'll find out the actual known issue and can follow it there. – Dan Wooding Jul 11 '17 at 23:43