Fix Save as Attachment failures in Flow Designer REST stepsIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } When creating a Flow Designer action that retrieves files from Jira and uploads them as attachments to ServiceNow records, the Save as Attachment feature may fail with a NullPointerException error. The following error appears in the logs: Operation(Upload Attachment.f9f7796edb476050002c3307f496195e) failed with error: java.lang.NullPointerExceptionat com.snc.process_flow.integration.MidAttachmentWrapper.saveResponseAsAttachment(MidAttachmentWrapper.java:118)at com.snc.process_flow.operation.AbstractHttpOperation.processResponseAttachment(AbstractHttpOperation.java:389)at com.snc.process_flow.operation.HttpOperation.processResponse(HttpOperation.java:287)at com.snc.process_flow.operation.AbstractHttpOperation.requestAndProcessResponse(AbstractHttpOperation.java:131)at com.snc.process_flow.operation.AbstractHttpOperation.invoke(AbstractHttpOperation.java:111)at com.snc.process_flow.operation.RetryableIntegrationOperation.run(RetryableIntegrationOperation.java:46)at com.snc.process_flow.engine.Operation.execute(Operation.java:165)at com.snc.process_flow.engine.ProcessEngine.executeOps(ProcessEngine.java:497)at com.snc.process_flow.engine.ProcessEngine.run(ProcessEngine.java:413)at com.snc.process_flow.engine.ProcessAutomation.run(ProcessAutomation.java:66)at com.snc.process_flow.engine.MidProcessAutomation.messageFlow(MidProcessAutomation.java:55)at com.service_now.mid.probe.IPaaSActionProbe.probe(IPaaSActionProbe.java:101)at com.service_now.mid.probe.AProbe.process(AProbe.java:104)at com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:122)at com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20)at com.service_now.mid.threadpool.ResourceUserQueue$RunnableProxy.run(ResourceUserQueue.java:647)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748) Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } All releases Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } To resolve the Save as Attachment failure in Flow Designer: Verify that your MID Server is running and properly validated.Check that the MID Server has permissions to read the table you use in the flow (for example, the incident table).To test MID Server permissions: Impersonate the MID Server userAccess the record in the user interface If the MID Server user cannot access the record, grant the appropriate permissions and test the flow action again. Note: For the incident table, you can disable the incident query business rule if it is not serving any purpose.