Scenarios using Custom Variables not working properly
Incident Report for Make
Resolved
This incident is now resolved.
Posted Jun 08, 2023 - 00:47 CEST
Update
We have applied a permanent fix on eu1.make.celonis.com and eu1.make.com, and based on our checks there are no issues and all scenarios are running as expected.
Posted Jun 07, 2023 - 21:32 CEST
Update
We are applying a fix for this issue.
Posted Jun 07, 2023 - 21:18 CEST
Update
We have applied a permanent fix on us1.make.celonis.com and us1.make.com, and based on our checks there are no issues and all scenarios are running as expected.

In regards to eu1.make.celonis.com and eu1.make.com, we are going to roll out the fix outside of business hours.
Please use the workaround as needed, it was described in the previous update.

We will post another update once a full fix is applied.
Posted Jun 07, 2023 - 13:13 CEST
Identified
We're currently experiencing an issue that appears only in certain unique circumstances when a running scenario is not properly using the values of team or organization variables during executions.

Specific circumstances for the issue are:
- A team or organization variable is used as a filter condition OR there is more than one team or organization variable referenced within a single mapped field, OR the variable is used inside a function.
- AND the scenario was created / modified before March 8, 2023
- AND the execution occurs after May 3, 2023

Workaround:
Any user encountering this issue can open the affected scenario, make any change (move a module) and hit save. This will immediately resolve the issue for that scenario.

Complete resolution:
The development team is actively working on a fix that will address any scenario where the issue still persists. Will post an update once we have more information around the permanent fix.
Posted Jun 06, 2023 - 11:39 CEST
Investigating
We're currently experiencing issues with Scenarios that use Custom Variables. Our engineering team is investigating the root cause.
Posted Jun 06, 2023 - 09:09 CEST
This incident affected: Website (eu1.make.com, us1.make.com, eu1.make.celonis.com, us1.make.celonis.com, make.com).