A field called “venue_name” and a request to fill “event_venue” look close enough to slip past in a long run. A misspelled field name is refused and nothing is written. Since 1.10.1 the error also names the fields it could not find, so you can see which one was wrong.
Better still is never sending the wrong name. Here the agent confirms the real names with you first, from an entry that already has them filled in.
I want ACF fields filled on some [Speaker] entries.
1. List the ACF field groups and note each field's key, label and type. That list does not show field names, so read the ACF fields on one existing Speaker entry, [ID 205], match its field names to the labels, and show me the match. Use only names I confirm.2. Read the current ACF values on these entries: [IDs 210, 214, 219].3. Fill these fields from what I give you here: [job title, company, LinkedIn URL for each speaker]. Do not invent a value I have not given.4. Show me a table: entry, field name, current value, new value. Wait for my yes.5. Write the approved values one entry at a time, sending only the fields in the table. If a write is refused because a field name is unknown, stop, show me the refusal, and write nothing more until we have checked the name.6. Read each entry back and confirm what was stored.Why this is safe to run
Steps 1 and 2 only read. The field group list returns structure, never stored values. Writes wait for your yes, go one entry at a time, and carry only the fields in the approved table, so nothing else on the entry is touched.
If a wrong name still gets through, the refusal stops the run, and the prompt tells the agent not to guess a replacement. Update post ACF fields is off until you enable it, it checks the connected user’s edit access to each entry, and every write lands in the Activity Log.
Already connected? Ask your agent to fill the ACF fields you list, and tell it to confirm the field names from an existing entry first.