Al usar la acción Add Attachment en Power Automate, estoy obteniendo el código de estado 500, lo que indica un problema del servidor. <\/P>
"body": {
Okay, this is officially closed.
The fix: Modify the timestamp within the file name to remove all colons ":". You can do this within Power Automate via the formatDateTime() expression. E.g., formatDateTime(utcNow(),'yyyy-MMM-dd HH-mm-ss')
As I mentioned, this changed overnight and is an undocumented requirement. Before this issue appeared, timestamps were allowed in file names (e.g., #:#). As of now, in my testing A:# and #:A both work, but #:# does not work.
Esri is unsure if this is intended behaviour or not. I requested that they update the documentation for this connector. IMO, best practice is to name your files as per Windows' Naming Files, Paths, and Namespaces.
From the simplified test I set-up. All I am doing is getting a file, and then trying to upload it.
Again, I can manually upload a file to this same FL. And in this same flow, I can even Query Attachment and Delete Attachment successfully:
It really is just "Add Attachment" that isn't working:
@abureaux That is weird, Can you share a screenshot of your Add attachment inputs. I am curious because, your delete attachment is working.
It could still be uploading/ creating a file that is somehow blocked.
We upgraded from 11.3 > 11.5 over a month ago. That is the only real change. There is a chance this particular flow, which is the only one using Add Attachment, hasn't run since 11.3. I forwarded the port diagram off to my IT for them to check.
Beyond that, server should be unchanged.
Same connector version as yours:
{ "statusCode": 400, "headers": { "ETag": "W/\"xyz\"", "arcgis_connector_version": "Enterprise 2025.2.0 2025.06.10 1749573699153 361de8", "X-Powered-By": "Express", "x-ms-environment-id": "default-xyz", "x-ms-tenant-id": "xyz", "x-ms-dlp-re": "-|-", "x-ms-dlp-gu": "-|-", "x-ms-dlp-ef": "-|-/-|-|-", "x-ms-mip-sl": "-|-|-|-", "Timing-Allow-Origin": "*", "x-ms-apihub-cached-response": "true", "x-ms-apihub-obo": "false", "Date": "Tue, 04 Nov 2025 21:41:23 GMT", "Content-Length": "91", "Content-Type": "application/json" }, "body": { "success": false, "message": "AxiosError: Request failed with status code 500. " } }
I don't have many ideas since you are saying that it was working previously. Has something changed on your Enterprise Security wise? Seems like Power Automate doesn't have access to your Enterprise or the feature layer. See if all the necessary ports for webhooks are open if you are using them:
ArcGIS Enterprise ports
Also, In the Raw outputs of the `Add Attachments` action what version do you see under
"arcgis_connector_version": "Enterprise 2025.2.0 2025.06.10 1749573699153 361de8",
@AkshayHarshe any ideas? I have opened a case today for this as the issue is ongoing and quite an issue.
Case number: 04039745
I will also add that this flow watches an inbox for lab results. Because this project only allows 1 set of lab results per year, I filter the record for attachments, and then delete all attachments from the current year. This is working properly. So it is finding the correct record in the correct layer and modifying it.
Here it is successfully deleting the attachment I manually uploaded, just moments before failing to upload that same attachment itself:
As mentioned, the 'Add attachment' step, but specifically for the Enterprise connector:
It's in a Do until to try until Success equals true
This is the extent of the explanation I get (raw json above), so not much to go off:
@abureaux That is interesting. Can you please share what steps are you running and what connector you are using?
Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
