Narrative:

My concern here is the time it took to be transferred to mx control after speaking with dispatch. I would like to report what an outstanding job [the] first officer did in support during the situation we had!towards the top of climb we received multiple cargo smoke ecams; which would come on and almost immediately disappear. The first one happened so fast we did not even see what it was. The duration of the second one was long enough to read and then it disappeared. We called the flight attendant's (flight attendants) to ask if they smelled anything in the back and sent an ACARS to mx advising of our issue and asking for troubleshooting/reset advice. The response from mx took longer than expected and we did not get the answer appropriate to our situation so we established a phone patch with dispatch to be connected to mx control. At that point the flight attendant's reported that they did not smell anything in the aft cabin. We were still waiting for the connection to mx control when an ACARS message was received stating; 'failed system is smoke detection function has failed. In the cids'.shortly after that we finally were able to speak to mx control and confirmed the ACARS that they had sent.mike and I discussed the situation agreeing that if the ECAM returned; even temporarily; we would land. We requested a reroute over the coast with dispatch as we were going to be heading out over the water. We coordinated with ATC and continued the flight to ZZZ without incident. After we parked the aircraft; we checked the status message which read; maintenance smoke.

Related reports:

Google
 

Original NASA ASRS Text

Title: A321 flight crew reported false Cargo Smoke Detector alerts in flight.

Narrative: My concern here is the time it took to be transferred to MX Control after speaking with dispatch. I would like to report what an outstanding job [the] First Officer did in support during the situation we had!Towards the top of climb we received multiple Cargo Smoke ECAMs; which would come on and almost immediately disappear. The first one happened so fast we did not even see what it was. The duration of the second one was long enough to read and then it disappeared. We called the FA's (Flight Attendants) to ask if they smelled anything in the back and sent an ACARS to MX advising of our issue and asking for troubleshooting/reset advice. The response from MX took longer than expected and we did not get the answer appropriate to our situation so we established a phone patch with dispatch to be connected to MX Control. At that point the FA's reported that they did not smell anything in the aft cabin. We were still waiting for the connection to MX Control when an ACARS message was received stating; 'failed system is smoke detection function has failed. In the cids'.Shortly after that we FINALLY were able to speak to MX control and confirmed the ACARS that they had sent.Mike and I discussed the situation agreeing that if the ECAM returned; even temporarily; we would land. We requested a reroute over the coast with dispatch as we were going to be heading out over the water. We coordinated with ATC and continued the flight to ZZZ without incident. After we parked the aircraft; we checked the status message which read; Maintenance Smoke.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.