I have a Zap set up to trigger several field updates in Airtable based on the content of a Slack Message in a specific Slack Channel.
The Zap formats the message, separating the text to allow for a searchable Airtable record name and a trigger phrase that is used to route the zap to one of 3 contextual paths, each path updating specific fields in the the search for air-table record based on specific criteria of that path.
In each of these paths the zap is meant to extract the timestamp from the posted slack message and format this into an Airtable local time format and to update a specific date field in Airtable with this information based on which path is triggered.
Every time I manually test and retest this process for all 3 paths the date field data is isolated, formatted and updated correctly in appropriate Airtable record based on the slack message trigger. Conversely, once the zap is out of test mode and is enabled the date field data does not update in the Airtable record as expected despite all other parts of the zap functioning normally to adjust other Airtable field in the record.
Can anyone explain what is going on? Surely if it works in all steps of testing it should behave similarly when enabled and running in the background.