FITsociety Help EN

Prevent duplicate changes in Make

3 min read

In this article

A Make scenario can run the same request again, for example after a timeout. For FITsociety write actions, you therefore use a fixed identifier for one change from your source system. In the FITsociety modules, this field may be called Source operation key.

If the same request is repeated with the same key and content, FITsociety can recognize the earlier outcome. This lowers the chance that a regular retry causes a second change. This recognition has a limited retention period and does not replace the checks in your scenario.

Choose a good key

Preferably use the unique event ID from the app that starts your scenario. Add a recognizable action. Examples with fictional IDs:

  • Create a new CRM member: crm:event-123:create-client.

  • Add a tag after a form submission: form:submission-456:add-tag.

  • Update a custom field after a FITsociety event: the event ID followed by :update-goal-field.

Map this value to the source field of the module meant for it. That way it stays the same on a repeated run. Do you use two steps for different changes within one event? Give each its own suffix, for example :update-field-a and :update-field-b.

When do you reuse the key?

Use the same key and the same input when you retry the same change after a failure. Use a new key for a genuinely new event or change.

Don't use the current time, a random ID or a run ID that changes on every attempt. Also don't use one fixed value for all members. Don't put names or email addresses in the key.

What do you do with error code 409?

An error code 409 can mean that a request is still being processed, that a record already exists or that the same key was used with different input.

First check the earlier run and the result in FITsociety. Don't change the key just to get around the error; that can still cause a duplicate change. On a retry, also compare the request content with the original input.

Retention period and permanent member identification

Recognition of Public API requests based on an idempotency key has a retention period of 24 hours. This is not unlimited deduplication of future runs. For events that may come in again later, also keep track in your scenario or source system of which event IDs have been processed.

Does your create module offer a permanent source ID for the member? Use a lasting member ID from your source system there. Store the link to the FITsociety member ID and use an update action for later changes. This recognition belongs to the access granted to your connection.

Did you revoke access and then reconnect? Look up existing members first. Don't just restart the original create steps: a new consent can also mean a new access context.

No connection yet? Read Connect FITsociety to Make.

Was this article helpful? Thanks for your feedback!

Thanks, we read every comment.

Related articles