It seems that Make’s Airtable → “Update a record” module will not update a record that was previously modified in an Airtable automation.
Scenario:
I have an Airtable database with a Single Select column from which I can generate an image through a Make automation.
The options are: “Generate image”, “Working…” and “Generated”.
Whenever a row is in a “Generate an image” view (filtered by the “Generate image” single select), an Airtable automation happens which starts a Make scenario to generate the image and updates the status to: “Working…”.
At the end of the scenario, Make tries to update the single select to “Generated”, along with other info. All the other info is updated except the single select.
If I remove the last step of the Airtable automation (updating the status to “Working…”), Make is able to update the field.
Solution: move the “Working…” status to the start of the Make automation.
I’m just adding this here in case someone needs the info.
Hello @vaidab,
First of all, I’m hoping that you’ve already set these options “Generate image”, “Working…” and “Generated”. in your Single Select field.
Airtable Single Select fields can’t able to generate(add) new options in run time while you update or add a new row. You have to set up option values before you try to do any operations.
Now there are a couple of things you can cross-check into Module settings.
→ Carefully check the spellings of these options on both sides which are given on the Make’s Airtable module.
→ Set Map option in the field setting is disabled.
→ When that Map option in the field setting is disabled then all options will appear on that setting field then select manually. Just select the option manually.
If this still has not solved your issues then please share your screenshot of the settings or error you’ve got.
P.S.: Always search first, Check Make Academy. If this is helpful, Mark Best Answers as Solutions and give If you need expert help or have questions? Contact or comment below!
Yes, I added them of course.
The spellings are correct, I also tried with and without Map.
Even with Map disabled and selecting the option, it doesn’t get updated.
Note that this is not an issue reporting, it’s a workaround due to a problem in the interaction.
You can replicate this on your end by:
creating a single select
creating an Airtable automation to launch a make scenario through a webhook, followed by an update to the single select
update the single select from the scenario after a delay (to make sure it doesn’t update before the airtable automation update)
Even though the scenario will work and 3) will run (showing as input/output that the cell is updated), Airtable will keep the value that was added through its own automation, even though the make scenario happens after.
If this was indeed the solution then you should mark your initial post as such, just so a conversation doesn’t continue about a non-issue.
It sounds like your Airtable automation and Make Scenario were conflicting, or experiencing a race condition.
By any chance, since your Airtable automation is firing a webhook, is it also waiting for a response? It doesn’t sound like the case, but if so, it may be waiting for that response before updating your Status field.
You may also consider modifying your automations to give you more visibility.
Might be a little overkill, but maybe add an “Initiated” status and have your Airtable automation simply change it to that. This way you’ll know the Airtable side of automations has run.
Move the Status change to Working… from Airtable to Make.
Make can then have a short waiting period, check that the image field is empty, and that the status is Initiated, and if so, proceed to change the status to Working…, create the image, change status to generated.
If the status gets stuck on Working… you’ll know that the Make automation ran but got stuck.
Many ways to handle it based on your goals, but just some thoughts!
When you update a field from Make’s automation it’s also considered as action and maybe it’s again fire that automation and change the value of it.
You need to cross-check check history of Airtable Automation as well as Make’s scenario.
If this happens then it also consumes more operations unnecessary.
Now you can apply what @Donald_Mitchell suggest.
OR
Use the Airtable automation trigger when “Record Matches Conditions”.
You can use a condition like when a Single Select is Generate image AND image field not blank, use all possible conditions which are not matched when you update the field from Make.
I hope you understand the concern.
Once again thanks @Donald_Mitchell for including that automation conflict concept.
P.S.: Always search first, Check 
and give 
If you need expert help or have questions? Contact or comment below! 