ISC Demo Tenant - Workflow Send Email step fails with 403 error when testing

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

I am trying to test a small workflow in my Ambassador Sandbox tenant. The workflow consists of 3 steps:

  • External Trigger
  • Send Email
  • End Success

I have configured the external trigger, and configured the Send Email to be hard coded with my email address and static subject and body. I have saved everything, closed and reopened it. When I click on “Test Workflow” and add my input of ‘{}’ I get a 403 Error as shown:

Screenshot 2024-05-17 at 1.33.40 PM
Screenshot 2024-05-17 at 1.33.40 PM1454×1011 82.9 KB

I found a similar mention of a 403 Error in a workflow doing GetIdentities here:

In that case, the issue was the owner did not have Org Admin privileges. I checked this, and my user is an org admin and the owner of the workflow.

I have tested this in the following environments and only one of them worked:

  • Ambassador Tenant without Demo Data - Failed
  • Ambassador Temp Tenant With Demo Data - Failed
  • Sandbox Tenant - Worked

The steps to reproduce are:

  • New Workflow from Builder
  • Add 3 steps: External trigger, Send Email Action, End Success
  • Configure Send Email with Hard coded values. Can configure External trigger, but not necessary.
  • Save workflow
  • Click Test Workflow and pass ‘{}’ for the input. Click Start Workflow Test.

It should either complete successfully or fail on the Send Email step with the 403. In both the successful and the failed tests, the external trigger was not configured.

Is anyone else experiencing this?

2

Hi, I saw that your sender is [email protected], I verified in my sandbox and it is [email protected]

I have had 403 errors in Send Email workflows when sender is not a verified email of Systme Settings.

Hope it is the case and helps.

3

So I just tested that, and it indeed works. I would have thought that the Test Workflow would have allowed that.

I also previously tried my own email there, which is the email configured on my Org-Admin user, and that failed also.

So I guess my next question is, what are considered Valid From email addresses?

In my Demo Ambassador Tenant I tried the following and they all Failed:

All of these gave the 403 error, which was not expected. For the Ambassador and Temp tenants, should the From email only be [email protected]?

4

I guess that only verified mails (the one that appears in system settings with the verified mark). That implies to verify the domain first and then the email address.

According to documentation, mails adresses with unverified domain can be verified too. If you enter any email, idn sends an email with a link to complete verification process. To be honest I never tried this option.

5

So I tested this out. I Vertified my Email address following the documentation. I have checked that it is set on the System Settings Page, and it is and marked Verified. When I try to do a Test Workflow, it is still failing with a 403. So the only option that doesn’t 403 seems to be “[email protected]”

Will validate again tomorrow incase it is a timing issue

6

Testing again this morning. The Verified Email address does in fact work now, so there is some delay longer than 5 minutes for it to propagate completely.

So @jsosa’s solution was correct, the email needs to be verified first before it can be used here without error AND you need to wait until the verification has propagated through, which is currently over 5 minutes, but less than 7 hours according to my experiences here.

1 Like
7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.