<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Why Webhook Transaction Settings Are Greyed Out in FusionAuth Cloud for User and Registration Events]]></title><description><![CDATA[<p dir="auto">I’m trying to configure a webhook that determines whether a user can self-service register for an application. This worked in my local FusionAuth instance, but I’m running into an issue in FusionAuth Cloud.</p>
<p dir="auto">In Cloud (v1.59.0), I cannot change the transaction setting for events like:</p>
<ul>
<li>user.registration.create</li>
<li>user.registration.delete</li>
<li>user.registration.update</li>
<li>user.registration.verified</li>
<li>user.update</li>
</ul>
<p dir="auto">In my local instance (v1.57.1), I was able to set the transaction behavior (for example, requiring all or some webhooks to succeed before continuing the transaction). In Cloud, those transaction options are greyed out.</p>
<p dir="auto">Why are these transaction settings disabled in FusionAuth Cloud?</p>
<p dir="auto">How can I re-enable the ability to configure them?</p>
<p dir="auto">Is this related to the version difference (1.59.0 Cloud vs 1.57.1 local), or something else?</p>
]]></description><link>https://fusionauth.io/community/forum/topic/3084/why-webhook-transaction-settings-are-greyed-out-in-fusionauth-cloud-for-user-and-registration-events</link><generator>RSS for Node</generator><lastBuildDate>Sun, 14 Jun 2026 19:07:22 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/3084.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 01 Jan 2026 03:38:55 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Why Webhook Transaction Settings Are Greyed Out in FusionAuth Cloud for User and Registration Events on Thu, 01 Jan 2026 03:39:19 GMT]]></title><description><![CDATA[<p dir="auto">This is a known bug, and it looks like the underlying issue has already been identified and fixed. The fix will be included in the next FusionAuth release.</p>
]]></description><link>https://fusionauth.io/community/forum/post/8462</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/8462</guid><dc:creator><![CDATA[wesley]]></dc:creator><pubDate>Thu, 01 Jan 2026 03:39:19 GMT</pubDate></item></channel></rss>